All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	intel-gfx@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] #1: test capitalizing PATCH
Date: Wed, 1 Mar 2017 00:57:07 +0300	[thread overview]
Message-ID: <20170228183804.GG4366@mwanda> (raw)
In-Reply-To: <87zih6cm4r.fsf@intel.com>

On Tue, Feb 28, 2017 at 06:31:48PM +0200, Jani Nikula wrote:
> 
> Cc: Hans, this probably applies to you as well.
> 
> On Tue, 28 Feb 2017, Dan Carpenter <dan.carpenter@oracle.com> 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.

Ah.  Great.  Thanks!

regards,
dan carpenter

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

  reply	other threads:[~2017-02-28 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 11:45 [PATCH] #1: test capitalizing PATCH Dan Carpenter
2017-02-28 16:31 ` Jani Nikula
2017-02-28 21:57   ` Dan Carpenter [this message]
2017-02-28 23:38   ` Hans de Goede
2017-03-01  9:57     ` Jani Nikula
2017-03-01 10:14       ` Hans de Goede

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=20170228183804.GG4366@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.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 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.