All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 00/10] Improve robustness of the i915 perf tests
Date: Tue, 29 Aug 2017 09:54:22 +0100	[thread overview]
Message-ID: <e86060ee-ea08-3a64-0cbf-8b90494e5cc6@intel.com> (raw)
In-Reply-To: <20170828142338.GC2446@ahiler-mobl1.igk.intel.com>

On 28/08/17 15:23, Arkadiusz Hiler wrote:
> 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 :-)
>
Thanks!

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2017-08-29  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  9:43 [PATCH v2 00/10] Improve robustness of the i915 perf tests Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 01/10] tests/perf: make stream_fd a global variable Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 02/10] tests/perf: add per context filtering test for gen8+ Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 03/10] tests/perf: update max buffer size for reading reports Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 04/10] tests/perf: rc6: try to guess when rc6 is disabled Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 05/10] tests/perf: remove frequency related changes Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 06/10] tests/perf: rework oa-exponent test Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 07/10] tests/perf: make enable-disable more reliable Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 08/10] tests/perf: make buffer-fill " Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 09/10] tests/perf: add Kabylake support Lionel Landwerlin
2017-08-23  9:43 ` [PATCH v2 10/10] tests/perf: add Geminilake support Lionel Landwerlin
2017-08-28  7:21 ` [PATCH v2 00/10] Improve robustness of the i915 perf tests Arkadiusz Hiler
2017-08-28 13:33   ` Lionel Landwerlin
2017-08-28 14:23     ` Arkadiusz Hiler
2017-08-29  8:54       ` Lionel Landwerlin [this message]

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=e86060ee-ea08-3a64-0cbf-8b90494e5cc6@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.