Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Hi Junio, On Mon, 16 Oct 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > >> >> -Also respects `:remotename` to state the name of the *remote* instead > >> >> of > >> >> -the ref. > >> >> +Also respects `:remotename` to state the name of the *remote*

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Johannes Schindelin writes: >> >> -Also respects `:remotename` to state the name of the *remote* instead of >> >> -the ref. >> >> +Also respects `:remotename` to state the name of the *remote* instead >> >> +of the ref, and `:remoteref` to state the name of the

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Hi, On Sat, 14 Oct 2017, Junio C Hamano wrote: > Kevin Daudt writes: > > > On Thu, Oct 05, 2017 at 02:19:15PM +0200, Johannes Schindelin wrote: > >> From: J Wyman > >> [..] > >> > >> diff --git a/Documentation/git-for-each-ref.txt > >>

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Hi Junio, On Fri, 13 Oct 2017, Junio C Hamano wrote: > Johannes Schindelin writes: > > >> (The funny "squash!" followed by a complete version of the > >> rewritten commit message is what I do until I -- or anybody else > >> -- comes up with a patch to implement

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Kevin Daudt writes: > On Thu, Oct 05, 2017 at 02:19:15PM +0200, Johannes Schindelin wrote: >> From: J Wyman >> [..] >> >> diff --git a/Documentation/git-for-each-ref.txt >> b/Documentation/git-for-each-ref.txt >> index 39f50bd53eb..22767025850 100644 >>

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

On Thu, Oct 05, 2017 at 02:19:15PM +0200, Johannes Schindelin wrote: > From: J Wyman > [..] > > diff --git a/Documentation/git-for-each-ref.txt > b/Documentation/git-for-each-ref.txt > index 39f50bd53eb..22767025850 100644 > --- a/Documentation/git-for-each-ref.txt > +++

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Johannes Schindelin writes: >> (The funny "squash!" followed by a complete version of the >> rewritten commit message is what I do until I -- or anybody else >> -- comes up with a patch to implement support for "reword!".) I have wished for something like that for a

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Hi Junio, On Wed, 11 Oct 2017, Junio C Hamano wrote: > Junio C Hamano <gits...@pobox.com> writes: > > > Johannes Schindelin <johannes.schinde...@gmx.de> writes: > > > >> Subject: Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally > >>

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Junio C Hamano <gits...@pobox.com> writes: > Johannes Schindelin <johannes.schinde...@gmx.de> writes: > >> Subject: Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally >> remote ref name > > No verb? s/optionally/report/ perhaps? I just noticed

Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

Johannes Schindelin <johannes.schinde...@gmx.de> writes: > Subject: Re: [PATCH v2 2/3] for-each-ref: let upstream/push optionally remote > ref name No verb? s/optionally/report/ perhaps? > diff --git a/ref-filter.c b/ref-filter.c > index 4819707d032..b4b2c9b2190 100644 &g

[PATCH v2 2/3] for-each-ref: let upstream/push optionally remote ref name

From: J Wyman There are times when scripts want to know not only the name of the push branch on the remote, but also the name of the branch as known by the remote repository. An example of this is when a tool wants to push to the very same branch from which it would pull