Re: setting up tracking on push

From: Jeff King <peff@peff.net>
Date: Mar 11, 2009, 03:57 UTC
Message-ID: <20090311035701.GA6089@coredump.intra.peff.net>
In-Reply-To: <76718490903102044j4ca3462eye5ffcb178608dc29@mail.gmail.com>

On Tue, Mar 10, 2009 at 11:44:14PM -0400, Jay Soffian wrote:

Show 5 quoted lines

> > Hmm. I think of that as "make <newbranch>, move from <oldbranch> or
> > HEAD".
> 
> Um, I think of it as "rename <oldbranch> to <newbranch>" where
> <oldbranch> defaults to the current branch (aka HEAD).

Perhaps it is because it was added onto "git branch" which already had an existing syntax and meaning, but I have always seen it as "operating" on the new branch.

There was some debate about this when "-m" came about (with respect to the order of arguments).

So I think it is largely a matter of perception and mental model.

> -u w/o --track/--no-track is a usage error.

Then what is the point of "-u"? You said before that it was a new operation with room for future growth of additional options. Either it is _just_ for --track, in which case I think you are better to have a single option representing the notion of "update the tracking setup", or it isn't, in which case it needs to have room for future expansion.

-Peff