Hi,
On 01-03-17 10:57, Jani Nikula wrote:
On Wed, 01 Mar 2017, Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
Hi,
On 28-02-17 17:31, Jani Nikula wrote:
Cc: Hans, this probably applies to you as well.
I'm already always using git-send-email, so whatever the
reason why the CI system is not picking up my patches, this
aint it.
It doesn't look like your patches match [1], though. Do you have the
sendemail.xmailer config option set to false?
Nope, just send myself a test patch:
Date: Wed, 1 Mar 2017 11:05:32 +0100
Message-Id: <20170301100532.26692-1-hdegoede@xxxxxxxxxx>
X-Mailer: git-send-email 2.9.3
Result: 250
But indeed the header is gone when it hits my own Inbox,
seems this gets stripped by the Red Hat smtp server somehow ?
I will file a ticket with our it department for this.
Regards,
Hans
BR,
Jani.
Regards,
Hans
On Tue, 28 Feb 2017, Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote:
The new version patchwork is filtering out my patches for some reason.
Test if it's because it now insists on a capital [PATCH] in the subject.
Patchwork should be more version control agnostic than that.
The patchwork flavor at freedesktop.org expects patches are sent using
git send-email [1]. I hear otherwise there were too many false
positives.
Please either use git send-email, or add
X-Mailer: git-send-email haha only kidding
header into your patch mails.
I'm sorry for the inconvenience and lack of transparency on
this. Apparently git send-email is so ubiquitous nowadays that this
hasn't been much of a problem.
BR,
Jani.
[1] https://github.com/dlespiau/patchwork/blob/master/patchwork/bin/parsemail.py#L323
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
