On Tue, Jan 13, 2015 at 02:28:13PM -0800, Junio C Hamano wrote:
> On the other hand, "I am forked from building on this one" done with
> "checkout -t" is an explicit mark the user leaves, so it would serve
> as a better hint to base the default heuristics on, I think.
>
> But nobody is asking for such a feature ;-)
FWIW, I very rarely run format-patch directly, but have a wrapper script
that dumps the patches into a tempfile and runs mutt. I taught it in
2007 to use the upstream branch as the default[1], and was puzzled
reading the start of this thread, thinking we already did that.
So that is perhaps not asking for the feature (I am already happy with
my homegrown wrapper), but is maybe an endorsement of it. :)
-Peff
[1] You may note in 2007 that we did not even have @{upstream}. I
implemented it manually using git-config! Then in 2009, I switched
it to use for-each-ref's "%(upstream)" placeholder. Literally 5 days
later, Dscho introduced @{upstream}, but I never got around to
switching. Maybe now it is time. :)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html