Thread (1 message) 1 message, 1 author, 2016-08-11

Re: git bug? + question

From: Shawn Pearce <hidden>
Date: 2016-08-11 20:18:12

Sean [off-list ref] wrote:
On Fri, 3 Nov 2006 15:29:45 -0500
Shawn Pearce [off-list ref] wrote:
quoted
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.
Agreed completely.  At least though with repo-config we have a
command line tool which users/scripts alike can use to read/edit
the configuration of a "remote"; .git/remotes/ has no such tool.

-- 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help