Re: [PATCH v6] Add git-grep threads param
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Nov 16, 2015, 21:17 UTC
- Message-ID
- <CAPig+cQMV-VJDff=VCeBqRLZC7Q42mu7T78_NK2TWLjEN-=cpw@mail.gmail.com>
- In-Reply-To
- <20151116135614.GA13471@sigill.intra.peff.net>
On Mon, Nov 16, 2015 at 8:56 AM, Jeff King <peff@peff.net> wrote:
Show 15 quoted lines
> On Mon, Nov 16, 2015 at 05:11:16AM -0800, Victor Leschuk wrote: > >> The earlier version of this patch is already included in /pu branch, >> however as we all agreed ($gmane/280299) we have changed the default >> behavior and the meaning of "0". The question is: what is the right >> way to include changes from patch v6 (this one) into already merged >> patch to pu? > > Merging to "pu" does not really mean anything; it is simply that the > maintainer has picked it up as a possible topic of interest. Patches can > (and often are) still re-written in that state. > > Junio is on vacation for a few weeks, and I'm acting as maintainer in > the interim. I've added your v6 to my pile of patches to look at, but I > haven't gone over it carefully yet.
To be perfectly explicit: Patches in 'pu' get replaced wholesale by newer versions, so you would simply send the new version of the patch in its entirety (as you did with v6).