Re: [PATCH 2/2] format-patch: introduce format.defaultTo

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jan 6, 2014, 20:42 UTC
Message-ID: <20140106204203.GI3881@google.com>
In-Reply-To: <CAEBDL5UaS2Hd-Yb417W+Fw_7j1+5sRAgszko-PbU7z901_X+cw@mail.gmail.com>

John Szakmeister wrote:

>                                                        I think in a
> typical, feature branch-based workflow @{u} would be nearly useless.

I thought the idea of @{u} was that it represents which ref one typically wants to compare the current branch to. It is used by 'git branch -v' to show how far ahead or behind a branch is and used by 'git pull --rebase' to forward-port a branch, for example.

So a topic branch with @{u} pointing to 'master' or 'origin/master' seems pretty normal and hopefully the shortcuts it allows can make life more convenient.

It is *not* primarily about where the branch gets pushed. After all, in both the 'matching' and the 'simple' mode, "git push" does not push the current branch to its upstream @{u} unless @{u} happens to have the same name.

Hoping that clarifies, Jonathan