Re: git bug? + question
- From
Sean <seanlkml@sympatico.ca>
- Date
- Nov 3, 2006, 21:27 UTC
- Message-ID
- <BAYC1-PASMTP020F825A42FB7A7DB6CD8BAEFE0@CEZ.ICE>
- In-Reply-To
- <20061103202945.GA7585@spearce.org>
On Fri, 3 Nov 2006 15:29:45 -0500 Shawn Pearce <spearce@spearce.org> wrote:
Show 10 quoted lines
> Nack. I'd rather see the entries added/removed from .git/config when > the branch is created/deleted, just like the ref and the reflog are > created/deleted. It makes behavior more consistent for the user > and it is mostly self documenting... > > "why is branch FOO pulling FOO by default? ahhh, its in > .git/config after git branch FOO FOO." > > Same goes for git-clone. The branch.master.merge=origin/master > entry should be in .git/config file after the clone is complete.
Well that's certainly an alternative implementation that achieves the same thing. The essential point is that most of the time the Git user should not have to manually create the merge entries in the config file. Git should be smart enough to get it right most of the time automatically.