From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: Ramkumar Ramachandra <artagnon@gmail•com>,
Git List <git@vger•kernel.org>
Subject: Re: [PATCH 2/2] format-patch: introduce format.defaultTo
Date: Tue, 07 Jan 2014 13:07:08 -0800 [thread overview]
Message-ID: <xmqqvbxvbiwz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140107205618.GA28102@sigill.intra.peff.net> (Jeff King's message of "Tue, 7 Jan 2014 15:56:18 -0500")
Jeff King <peff@peff•net> writes:
> Yes, "pushbranch" is probably a better name for what I am referring to.
> I agree that pushremote is probably enough for sane cases. I seem to
> recall that people advocating the "upstream" push-default thought that
> branch name mapping was a useful feature, but I might be
> mis-remembering. I will let those people speak up for the feature if
> they see fit; it seems somewhat crazy to me.
I think "branch mapping" you recall are for those who want to push
their 'topic' to 'review/topic' or something like that. With Git
post 7cdebd8a (Merge branch 'jc/push-refmap', 2013-12-27), I think
"remote.*.push" can be used to implement that, by the way.
>> Frankly, I don't use full triangular workflows myself mainly because
>> my prompt is compromised: when I have a branch.*.remote different from
>> branch.*.pushremote, I'd like to see where my branch is with respect
>> to @{u} and @{publish} (not yet invented);
>
> Yes, as two separate relationships, you would theoretically want to be
> able to see them separately (or simultaneously side by side). Whether
> exposing that in the prompt is too clunky, I don't know (I don't even
> show ahead/behind in my prompt, but rather prefer to query it when I
> care; I have a separate script that queries the ahead/behind against my
> publishing point, but it would be nice if git handled this itself).
Same here. I do not bother a/b in prompt and comparison with
publishing point is done with a custom script. It would be nice to
have it natively, and @{publish} would be a good first step to do
so.
next prev parent reply other threads:[~2014-01-07 21:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 17:18 [PATCH 0/2] Minor convinience feature: format.defaultTo Ramkumar Ramachandra
2014-01-06 17:18 ` [PATCH 1/2] completion: complete format.coverLetter Ramkumar Ramachandra
2014-01-07 11:24 ` Ramkumar Ramachandra
2014-01-06 17:18 ` [PATCH 2/2] format-patch: introduce format.defaultTo Ramkumar Ramachandra
2014-01-06 18:35 ` Jonathan Nieder
2014-01-06 19:02 ` Ramkumar Ramachandra
2014-01-06 18:42 ` Junio C Hamano
2014-01-06 18:49 ` Ramkumar Ramachandra
2014-01-06 20:06 ` Junio C Hamano
2014-01-06 20:18 ` Jeff King
2014-01-06 20:29 ` John Szakmeister
2014-01-06 20:42 ` Jonathan Nieder
2014-01-06 21:13 ` John Szakmeister
2014-01-06 21:37 ` Junio C Hamano
2014-01-06 22:54 ` Ramkumar Ramachandra
2014-01-07 0:42 ` John Szakmeister
2014-01-07 16:47 ` Ramkumar Ramachandra
2014-01-06 20:43 ` Jeff King
2014-01-06 20:38 ` Junio C Hamano
2014-01-06 20:55 ` Jeff King
2014-01-06 21:21 ` Junio C Hamano
2014-01-06 22:10 ` Ramkumar Ramachandra
2014-01-07 20:56 ` Jeff King
2014-01-07 21:07 ` Junio C Hamano [this message]
2014-01-07 21:24 ` Jeff King
2014-01-07 22:06 ` Junio C Hamano
2014-01-07 22:17 ` Jeff King
2014-01-07 22:27 ` Junio C Hamano
2014-04-10 19:17 ` Felipe Contreras
2014-01-06 21:59 ` Ramkumar Ramachandra
2014-01-06 22:22 ` Junio C Hamano
2014-01-06 22:47 ` Ramkumar Ramachandra
2014-01-07 21:06 ` Jeff King
2014-01-07 21:25 ` Ramkumar Ramachandra
2014-01-07 21:30 ` Jeff King
2014-04-10 19:20 ` Felipe Contreras
2014-01-06 17:25 ` [PATCH 0/2] Minor convinience feature: format.defaultTo Ramkumar Ramachandra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqvbxvbiwz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=artagnon@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox