From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org,
Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Subject: Re: [PATCH] dim: Accept author x signed-off based on email, but warn.
Date: Wed, 20 Sep 2017 14:51:50 +0300 [thread overview]
Message-ID: <87mv5p7fl5.fsf@nikula.org> (raw)
In-Reply-To: <1505905347.8291.2.camel@linux.intel.com>
On Wed, 20 Sep 2017, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
> On Tue, 2017-09-19 at 10:48 -0700, Rodrigo Vivi wrote:
>> It seems Patchwork or SMTP servers are messing some patches
>> and changing the original git's author name on git per "Last, First".
>> So we end up with a mismatch were signed-off uses one name format
>> and author is using another format.
>
> + Arek,
>
> Wasn't this trouble supposed to be fixed?
Maybe in patchwork context, but it can still happen for people applying
patches from their MUA. And I doubt it can be reliably "fixed" if the
author intentionally or inadvertently has differing author and sob
lines.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-20 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 17:48 [PATCH] dim: Accept author x signed-off based on email, but warn Rodrigo Vivi
2017-09-20 7:56 ` Jani Nikula
2017-09-20 11:02 ` Joonas Lahtinen
2017-09-20 11:51 ` Jani Nikula [this message]
2017-09-20 12:46 ` Rodrigo Vivi
2017-09-20 12:49 ` [PATCH] dim: Accept author x signed-off based on email Rodrigo Vivi
2017-09-21 11:12 ` Jani Nikula
2017-09-21 13:27 ` Rodrigo Vivi
2017-09-26 11:59 ` Daniel Vetter
2017-09-26 13:24 ` Jani Nikula
2017-09-26 16:55 ` Rodrigo Vivi
2017-09-27 12:14 ` Daniel Vetter
2017-09-27 15:39 ` Rodrigo Vivi
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=87mv5p7fl5.fsf@nikula.org \
--to=jani.nikula@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).