From: Bruce D'A. <bd...@gm...> - 2011-02-01 20:11:20
|
On Tue, Feb 1, 2011 at 3:05 PM, Kieren Diment <di...@gm...> wrote: > > On 02/02/2011, at 12:43 AM, Bruce D'Arcus wrote: > >> On Sat, Jan 29, 2011 at 7:40 PM, Bruce D'Arcus <bd...@gm...> wrote: >> >> ... >> >>> Not really sure why they emphasize both forking and branching though, >>> but I sense it's important to understand. >> > > > Forking is just making your own copy of the repository. As every git repository is a self contained complete repository (distributed VCS) it's a bit like if everybody was contributing to the same project using a completely different svn server then merging at key points. Yes I know that; particularly so with mercurial. But git has in-repo branches as well, and in this case, the project suggests simultaneously forking the repo and doing the changes on a branch within that fork. It seems like effectively double-branching (and so redundant), but assume there must be a reason for it. Bruce |