just thought I'd pop by here and post a little "keep a local copy of
p2pool up to date" I noticed windpath back there with a
rm -rf p2pool ; git clone p2pool - shocking display man!
Now you want to cruise over to the hub to grab mainline p2pool as in
forrestv's p2pool. You can fork it there with one click. An account
there allows you to push changes to the hub but probably, not possibly only
makes sense if your actively developing and or contributing to the project.
You can definately clone p2pool and still keep it updated locally anyway.
Once thats done its time to party. If your on linux your laughing this can
all be done at the console.
Adjust these commands to suit your personal rig.
mkdir $HOME/mining
cd $HOME/mining
git clone --bare git@github.com:Polyatomic/p2pool.git
That there becomes your authoritative git or depot if you like. No
work gets done in there - We'll create a working repo for that now.
Adjust accordingly
git clone $HOME/miner/p2pool.git
- notice the extention
bam that becomes your working repository and by default maintains a link
back to its parent repository which is p2pool.git
cd p2pool(working repository)
The command used to manipulate and create a remote is `git remote` lets
introduce a remote, which will be forrestv's p2pool I'll call it mainline.
As usual on linux there are many ways to do the same thing.
git remote add mainline git@github.com:forrestv/p2pool.git
git remote update mainline
or
git remote add mainline git@github.com:forrestv/p2pool.git
git remote fetch mainline
or the more compact
git remote add -f mainline git@github.com:forrestv/p2pool.git
check it out!
milton@milton:~/temp/p2pool$ git remote add -f mainline git@github.com:forrestv/p2pool.git
Fetching origin
Enter passphrase for key '/home/milton/.ssh/id_rsa':
Fetching mainline
Enter passphrase for key '/home/milton/.ssh/id_rsa':
remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0), pack-reused 1
Unpacking objects: 100% (1/1), done.
From github.com:forrestv/p2pool
* [new branch] badblock -> mainline/badblock
* [new branch] fast_sha -> mainline/fast_sha
* [new branch] hardfork -> mainline/hardfork
* [new branch] litecoindust -> mainline/litecoindust
* [new branch] master -> mainline/master
* [new branch] memory -> mainline/memory
* [new branch] novacoin -> mainline/novacoin
* [new branch] rav -> mainline/rav
* [new branch] tmp -> mainline/tmp
* [new branch] worker_check -> mainline/worker_check
* [new tag] 14.0 -> 14.0
milton@milton:~/temp/p2pool$ git branch -a
* Polyatomic
remotes/mainline/badblock
remotes/mainline/fast_sha
remotes/mainline/hardfork
remotes/mainline/litecoindust
remotes/mainline/master
remotes/mainline/memory
remotes/mainline/novacoin
remotes/mainline/rav
remotes/mainline/tmp
remotes/mainline/worker_check
remotes/origin/HEAD -> origin/Polyatomic
remotes/origin/Polyatomic
remotes/origin/badblock
remotes/origin/fast_sha
remotes/origin/hardfork
remotes/origin/litecoindust
remotes/origin/master
remotes/origin/memory
remotes/origin/novacoin
remotes/origin/rav
remotes/origin/tmp
remotes/origin/worker_check
Success, see that up there.
If you want to make changes create your own branch. The name you assign to your
branch can be anything, arbitrary even. The default branch which is master needs
to remain robust and dependable.
git branch Polyatomic ; git checkout Polyatomic
or the more compact
git checkout -b Polyatomic
When mainline p2pool gets updated by the developer all you have to do is
git fetch mainline
git checkout master - if your on your own branch
git merge mainline/master
git will perform a fastforward
Updating 0bc89a2..f266042
Fast-forward
p2pool/bitcoin/helper.py | 7 ++-
p2pool/data.py | 341 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------
p2pool/networks/bitcoin.py | 4 +-
p2pool/p2p.py | 2 +-
p2pool/test/test_node.py | 10 ++--
p2pool/work.py | 2 +-
6 files changed, 338 insertions(+), 28 deletions(-)
And if you want to keep your fork updated at the hub this is where the depot
comes in handy remember the p2pool with the .git extension. Lets move HEAD forward
a bit. Move into your working repository
milton@milton:~/temp/p2pool$ touch testing ; echo "testing" > testing ; git add testing ; git commit -m "testing" -m ""
[Polyatomic 9478c49] testing
1 file changed, 1 insertion(+)
create mode 100644 testing
Now push to the depot
milton@milton:~/temp/p2pool$ git push origin
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 454 bytes | 0 bytes/s, done.
Total 5 (delta 2), reused 0 (delta 0)
To /home/milton/temp/p2pool.git/
f266042..9478c49 Polyatomic -> Polyatomic
notice the extension upthere and if you want to push that commit up to the github , change into the
authoritative repo, do exactly the same
cd p2pool.git
git push origin
or if you only want to push a branch
git push origin [branchname]
If this post is offensive to anyone in here, a duplicate post maybe or it just sux in general, say so and I'll
delete it. Take it easy
full blown bip066 man!
