Re: [PATCH 0/2] Making "git commit" to mean "git commit -a".
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 30, 2006, 22:55 UTC
- Message-ID
- <Pine.LNX.4.63.0611302354060.30004@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <7vac28h898.fsf@assigned-by-dhcp.cox.net>
Hi,
On Thu, 30 Nov 2006, Junio C Hamano wrote:
Show 17 quoted lines
> Linus Torvalds <torvalds@osdl.org> writes: > > > ... > > So yes, you very much ARE talking about CVS braindamage. The reason why > > > > git add file.c > > echo New line >> file.c > > git commit > > > > commits the _old_ content, is very much because git is ALL ABOUT THE > > CONTENT. It has _never_ been about filenames. And it _shouldn't_ be about > > filenames, because that would be BUGGY AND BROKEN. > > I think this pretty much sums up and closes the current topic, > by declaring "expecting to give behaviour consistent to the > 'filename is what the user tells the SCM to track' mental model > CVS instilled is a lost cause".
I think this is so important, that I vote for including this email as Documentation/howto/explain-why-git-is-better-than-cvs.txt
Ciao, Dscho