Re: git bug? + question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 3 Nov 2006 15:29:45 -0500
Shawn Pearce <spearce@xxxxxxxxxxx> wrote:

> 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.

Sean
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]