Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: i-g-t/libdrm email tagging & patchwork
Date: Thu, 19 Nov 2015 17:21:34 +0200	[thread overview]
Message-ID: <87si42t3pd.fsf@intel.com> (raw)
In-Reply-To: <20151119150741.GE3002@strange.ger.corp.intel.com>

On Thu, 19 Nov 2015, Damien Lespiau <damien.lespiau@intel.com> wrote:
> On Thu, Nov 19, 2015 at 12:44:07PM +0200, Jani Nikula wrote:
>> On Wed, 18 Nov 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
>> > On Sun, Nov 08, 2015 at 12:31:36AM +0000, Damien Lespiau wrote:
>> >> Hi all,
>> >> 
>> >> I've added a feature to sort the patches sent to intel-gfx into 3
>> >> buckets: i915, intel-gpu-tools and libdrm. This sorting relies on
>> >> tagging patches, using the subject prefixes (which is what most people
>> >> do already anyway).
>> >> 
>> >>   - i915 (intel-gfx): catchall project, all mails not matching any of
>> >>     the other 2 projects will end up there
>> >> 
>> >>   - intel-gpu-tools: mails need to be tagged with i-g-t, igt or
>> >>     intel-gpu-tools
>> >> 
>> >>   - libdrm-intel: mails need to be tagged with libdrm
>> >> 
>> >> This tagging can be set up per git repository with:
>> >> 
>> >>   $ git config format.subjectprefix "PATCH i-g-t"
>> >
>> > Is there any way we could push this out to users somehow? I have bazillion
>> > of machines, I'll get this wrong eventually ... So will everyone else I
>> > guess.
>> 
>> Googling around, I don't think we can automatically force this on
>> people. We could add a script to make it easier for people to set this
>> up. Either a setup that needs to be re-run every time there are changes,
>> or a setup that symlinks a git hook back into a file stored in the
>> repository so changes are deployed automatically. The latter has
>> security implications, so I'd go for the former.
>
> So, we could have:
>
>   $ git pw init https://patchwork.freedesktop.org/ intel-gpu-tools
>
> which would retrieve some server side config and shove it into
> .gitconfig. That does require a step anyway though, not sure how ideal
> this is or what else could be interesting to do with such a thing.

I like the idea of making this specific to patchwork (the git subcommand
and the server/project) rather than a some magic in the repository of a
project. Much more generic that way.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-11-19 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08  0:31 i-g-t/libdrm email tagging & patchwork Damien Lespiau
2015-11-09  8:45 ` Jani Nikula
2015-11-09 11:06   ` Damien Lespiau
2015-11-09 11:21     ` Jani Nikula
2015-11-09 11:22       ` Damien Lespiau
2015-11-18 10:56 ` Daniel Vetter
2015-11-18 15:53   ` Paulo Zanoni
2015-11-19 10:44   ` Jani Nikula
2015-11-19 15:07     ` Damien Lespiau
2015-11-19 15:21       ` Jani Nikula [this message]
2015-11-19 15:26       ` Morton, Derek J

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=87si42t3pd.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=damien.lespiau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox