{"thread":{"id":"5455","subject":"Suggestions for my use case","startedAt":"2006-09-02T14:41:23Z","lastAt":"2006-09-02T14:41:23Z","messageCount":1,"participants":["Russell"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"26222","messageId":"c1b8b6670609020741q2d45ea3nf336611edcd452b6@mail.gmail.com","threadId":"5455","inReplyTo":null,"subject":"Suggestions for my use case","fromName":"Russell","fromEmail":"russellsteicke@gmail.com","sentAt":"2006-09-02T14:41:23Z","receivedAt":"2006-09-02T14:41:23Z","isPatch":false,"sender":{"key":"russellsteicke@gmail.com","avatar":null},"body":"Hello,\n\nI've been tring git for a few private projects and have come up with a\nway to organise distributed development on multiple machines.  I was\nwondering if anyone else could comment on what I've done?  Here it\nis...\n\nI want to be able to work on a project called proj on multiple\ncomputers, and have backups on removable media.  Let's say I have\ncomputers c1 and c2, and a removable hard disk labelled disk1.  I've\nsetup the repositories in\n\n  c1: /home/me/proj\n  c2: /home/me/proj\n  disk1: /media/disk1/me/proj\n\nIn c1:/home/me/proj/.git/remotes/c2\n  URL: ssh://c2/home/me/proj\n  Pull: refs/heads/master:refs/heads/host/c2\n  Push: refs/heads/master:refs/heads/host/c1\n\nIn c1:/home/me/proj/.git/remotes/disk1\n  URL: /media/disk1/me/proj\n  Pull: refs/heads/master:refs/heads/disk/disk1\n  Push: refs/heads/master:refs/heads/host/c1\n\nIn c2:/home/me/proj/.git/remotes/c1\n  URL: ssh://c1/home/me/proj\n  Pull: refs/heads/master:refs/heads/host/c1\n  Push: refs/heads/master:refs/heads/host/c2\n\nIn c2:/home/me/proj/.git/remotes/disk1\n  URL: /media/disk1/me/proj\n  Pull: refs/heads/master:refs/heads/disk/disk1\n  Push: refs/heads/master:refs/heads/host/c2\n\nc1 has these branches:\n  master\n  host/c2\n  disk/disk1\n\nc2 has these branches:\n  master\n  host/c1\n  disk/disk1\n\ndisk1 has these branches:\n  master\n  host/c1\n  host/c2\n\nSo after doing some work at c1 and committing into master, I can\n  c1$ git-push c2\n  c1$ git-push disk1\n\nThen when I sit down at c2:\n  c2$ git-pull . host/c1\n\nOr if I've forgotten to push from c1:\n  c2$ git-pull c1\n\nOr I can cart disk1 around, and\n  c2$ git-pull disk1\n\nEach repository stays on its master branch.  As per the git-pull man\npage, no development is done on branches that I pull from.\n\nThis is working fine for me at the moment, which is single person\ndevelopment, straight line, no branching.  When I come to branches, I\nthink the branches will need to be added in each repository, with push\nand pull lines in .git/remotes/c1 etc.\n\nDoes this look reasonable?  What have I missed that would make this\nmore manageable, particularly with respect to branching?\n\n-- \nVGER BF report: U 0.500329\n"}]}