Re: defaults for where to merge from

"Alex Riesen" [off-list ref] writes:

quoted

If everyone hated the old behavior, old users should already be careful
about not git-pull'ing (without options) from any branch but master.  So
they won't see any difference.

except for .git/config growing uncontrollably

I think this should be a new option, not the _modified default_.
Otherwise it would be harder to sell to olde timers.

	$ git checkout -B <newbranch> remotes/<blah>
        $ git branch --track <newbranch> remotes/<blah>

might be a good compromise.

On Thu, Mar 01, 2007 at 12:18:58AM -0800, Junio C Hamano wrote:

"Alex Riesen" [off-list ref] writes:

quoted

quoted

If everyone hated the old behavior, old users should already be careful
about not git-pull'ing (without options) from any branch but master.  So
they won't see any difference.

except for .git/config growing uncontrollably

I think this should be a new option, not the _modified default_.
Otherwise it would be harder to sell to olde timers.

	$ git checkout -B <newbranch> remotes/<blah>
        $ git branch --track <newbranch> remotes/<blah>

might be a good compromise.

Personally I usually use <blah> as <newbranch>.  I might have gone for
something like

	git remote checkout [remote] blah [-b newbranch]

with defaulted to newbranch = blah.

--b.