Jeff King [off-list ref] writes:
On Thu, Sep 10, 2009 at 12:18:06PM +0200, Johan Herland wrote:
quoted
quoted
quoted
A special shortcut '@{tracked}' refers to the branch tracked by the
current branch.
Sorry, I didn't know the name of the long form was up for discussion.
But it should certainly coincide with the key which for-each-ref
uses, shouldn't it? I don't care whether tracked or upstream, but
for-each-ref's "upstream" has set the precedent.
...and 'git branch --track' set an even earlier precedent...
FWIW, that came about from this discussion:
http://article.gmane.org/gmane.comp.version-control.git/115765
After re-reading the discussion in the thread that contains the quoted
article, it sounds like we may want to fix "branch --track X Y". X does
not "track" Y in the same sense as origin/master "tracks" master at
origin. Rather, X builds on Y.