[Intel-gfx] [PATCH v2 00/10] Improve robustness of the i915 perf tests

[Arkadiusz Hiler]

On Mon, Aug 28, 2017 at 02:33:13PM +0100, Lionel Landwerlin wrote:
> On 28/08/17 08:21, Arkadiusz Hiler wrote:
> > On Wed, Aug 23, 2017 at 10:43:08AM +0100, Lionel Landwerlin wrote:
> > > Hi all,
> > > 
> > > Here is an updated patch series containing mostly cleanups.
> > > 
> > > Cheers,
> > Hi,
> > 
> > Our CI hasn't pick this series up for a spin due to missing a "i-g-t" tag.
> > 
> > Direct quote from CONTRIBUTING file:
> > -----------------------------------------------------------------------------
> > Please use --subject-prefix="PATCH i-g-t" so that i-g-t patches are easily
> > identified in the massive amount mails on intel-gfx. To ensure this is always
> > done, autogen.sh will run:
> > 
> > git config format.subjectprefix "PATCH i-g-t"
> > 
> > on its first invocation.
> > -----------------------------------------------------------------------------
> > 
> > 
> If only there was a wrapper around git (much like chromium has git cl), it's
> too easy to get this stuff wrong when you want to send a v2 and you have to
> use --subject-prefix :/


Luckily there is, quote from man git-format-patch:

------------------------------------------------------------------------
-v <n>, --reroll-count=<n>
    Mark the series as the <n>-th iteration of the topic. The output
    filenames have v<n> prepended to them, and the subject prefix
    ("PATCH" by default, but configurable via the --subject-prefix
    option) has ` v<n>` appended to it. E.g.  --reroll-count=4 may
    produce v4-0001-add-makefile.patch file that has "Subject: [PATCH v4
    1/20] Add makefile" in it.
------------------------------------------------------------------------

I wasn't aware of that until recently I found as an usage example posted
on some internet forum and was really surprised it an option :-)

-- 
Cheers,
Arek