Re: If merging that is really fast forwarding creates new commit [Was: Re: how to show log for only one branch]
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Nov 7, 2006, 16:39 UTC
- Message-ID
- <eiqcqn$c0$1@sea.gmane.org>
- In-Reply-To
- <Pine.LNX.4.64.0611070729370.3667@g5.osdl.org>
Linus Torvalds wrote:
Show 6 quoted lines
> So doing a merge doesn't really "centralize" anything. It just joins the > two development threads together in that particular line. If "master" > merges the work in "maint", master doesn't really get any more > centralized, it just gets the work that "maint" did since last time. And > if there was no other work done at all, then the two branches end up 100% > identical - there was no "merge" of the work.
By the way, merges happen in _two_ directions. 'Master' merges from 'next' when 'next' is in sufficiently stable state; 'next' merges from 'master' to get changes which were considered stable enough to be put into 'master' (and 'master' merges in from 'maint', too).
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git