Re: Workflow question
- From
Karl Hasselström <kha@treskal.com>
- Date
- Sep 26, 2007, 01:51 UTC
- Message-ID
- <20070926015146.GA25175@diana.vm.bytemark.co.uk>
- In-Reply-To
- <20070926004734.GA22617@segfault.peff.net>
On 2007-09-25 20:47:34 -0400, Jeff King wrote:
Show 7 quoted lines
> Personally, I think it pays to learn a little about what's going on > under the hood, and then all of the commands Just Make Sense. > > There are several explanations floating around; this is a pretty > concise one: > > http://eagain.net/articles/git-for-computer-scientists/
I agree. Once you understand that history in git is just a DAG of commits, and that "branches" are just named pointers into this DAG to help the user remember where to attach new commits, everything starts to Just Make Sense.
(And FWIW, that article was quite good as I recall.)
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle