From: George Dunlap <george.dunlap@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/3] Don't accept fuzz when patching
Date: Mon, 13 Jun 2016 11:57:44 +0100 [thread overview]
Message-ID: <CAFLBxZYAA3YPtrDThw_x+fbV9qe+5Z5-p--VCoepmerQwtzy-A@mail.gmail.com> (raw)
In-Reply-To: <575E87F4.6080205@citrix.com>
On Mon, Jun 13, 2016 at 11:16 AM, Andrew Cooper
<andrew.cooper3@citrix.com> wrote:
> On 13/06/16 11:08, George Dunlap wrote:
>> On Fri, Jun 10, 2016 at 12:02 PM, Ross Lagerwall
>> <ross.lagerwall@citrix.com> wrote:
>>> When testing and applying patches, set fuzz=0 so that patches must apply
>>> exactly. Also set "-f" to avoid interactive questions, and reorder so
>>> that patches are tested before the output directory is created.
>>>
>>> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
>>> ---
>>> livepatch-build | 11 +++++------
>>> 1 file changed, 5 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/livepatch-build b/livepatch-build
>> I take it this is in the "livepatch" repo, not the core Xen repo?
>>
>> I think unless / until livepatch has its own mailing list, all patches
>> sent to xen-devel to the livepatch should be prefixed with
>> "livepatch:", so that people can filter them properly. I realize
>> this is a bit annoying as then when doing "git log" inside of
>> livepatch.git, you see "livepatch:" at the beginning of every line;
>> but I think it's worth it. That's what raisin does, FWIW.
>
> An alternative is to use git format-patch --subject-prefix="PATCH livepatch"
>
> This puts livepatch into the email subjects, but gets stripped when
> applying the patch.
Yes, this is a better idea, thanks.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-13 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 11:02 [PATCH 1/3] Don't accept fuzz when patching Ross Lagerwall
2016-06-10 11:02 ` [PATCH 2/3] Update to use a .config file Ross Lagerwall
2016-06-14 15:35 ` Konrad Rzeszutek Wilk
2016-06-15 8:08 ` Ross Lagerwall
2016-06-15 14:00 ` Konrad Rzeszutek Wilk
2016-07-14 8:05 ` Ross Lagerwall
2016-07-15 13:36 ` Konrad Rzeszutek Wilk
2016-07-16 1:55 ` Konrad Rzeszutek Wilk
2016-07-18 9:33 ` Ross Lagerwall
2016-07-18 10:28 ` Konrad Rzeszutek Wilk
2016-06-10 11:02 ` [PATCH 3/3] Update README.md Ross Lagerwall
2016-06-14 15:36 ` Konrad Rzeszutek Wilk
2016-06-13 10:08 ` [PATCH 1/3] Don't accept fuzz when patching George Dunlap
2016-06-13 10:16 ` Andrew Cooper
2016-06-13 10:57 ` George Dunlap [this message]
2016-06-13 10:23 ` Ross Lagerwall
2016-06-14 15:33 ` Konrad Rzeszutek Wilk
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=CAFLBxZYAA3YPtrDThw_x+fbV9qe+5Z5-p--VCoepmerQwtzy-A@mail.gmail.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).