From: Dan Carpenter <dan.carpenter@oracle.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [patch] #2: test adding ---
Date: Tue, 28 Feb 2017 15:18:30 +0300 [thread overview]
Message-ID: <20170228121830.GF4366@mwanda> (raw)
In-Reply-To: <20170228121019.GO10304@nuc-i3427.alporthouse.com>
On Tue, Feb 28, 2017 at 12:10:19PM +0000, Chris Wilson wrote:
> On Tue, Feb 28, 2017 at 02:46:18PM +0300, Dan Carpenter wrote:
> > The new version of patchwork is filtering out my patches which apply
> > fine with git am and have worked for everyone else's patchwork. Perhaps
> > it's insisting on a --- break?
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > ---
>
> iirc, pw does insist on ---
It doesn't for anyone else. It shouldn't. But that doesn't mean you're
wrong...
regards,
dan carpenter
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-02-28 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 11:46 [patch] #2: test adding --- Dan Carpenter
2017-02-28 12:10 ` Chris Wilson
2017-02-28 12:18 ` Dan Carpenter [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=20170228121830.GF4366@mwanda \
--to=dan.carpenter@oracle.com \
--cc=chris@chris-wilson.co.uk \
--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.