Re: [PATCH] Documentation: update git-pull.txt for clone's new default behavior

["J. Bruce Fields" <bfields@fieldses.org>]

On Sun, Dec 31, 2006 at 09:13:49PM -0800, Luben Tuikov wrote:
> Yes, but I don't want to just type "git-pull", I want to explicitly
> type "git-pull parent" and depending in which branch I'm at, "parent"
> would have identical meaning but would merge a different branch... because
> I'm in a different branch...

Wouldn't it do what you want if by default "git branch new" and "git
checkout -b new" set branch.* options that pointed at the "parent"
branch?

The only reason I can see to require the extra bit of syntax ("git-pull
parent" instead of "git-pull") is if for the same branch you expect to
sometimes pull from one source and sometimes from another, and the pulls
from those various sources are common enough that it's worth defining
some shortcuts for more than one of them.

I can imagine sometimes doing that.  (E.g. if you pull into your master
branch from upstream and from local topic branches.)  But in that case
having to give the remote and branch name explicitly doesn't seem so
bad.

I dunno....

--b.