From: Stefano Stabellini <sstabellini@kernel.org>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 01/11] public: adjust documentation following XSA-217
Date: Wed, 21 Jun 2017 10:55:39 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1706211054070.12819@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <439da63f-913f-4a3b-2de1-5b5c8d46fb27@citrix.com>
On Wed, 21 Jun 2017, George Dunlap wrote:
> On 21/06/17 16:54, Jan Beulich wrote:
> >>>> On 21.06.17 at 17:44, <george.dunlap@citrix.com> wrote:
> >> When you have a long series like this, could you name the files in a way
> >> that makes it easier for a shell script to get their order? e.g.,
> >> 01-xsa217-doc.patch, 02-gnttab-xfer-xenheap.patch, &c?
> >>
> >> Having to manually save-and-apply the name of each patch of an
> >> eleven-patch series separately is fairly annoying. If they started with
> >> a number, I could save them all to the same directory and then use "for
> >> patch in *.patch ; do..." to apply them.
> >>
> >> (Using `git send-email` would also make things a lot easier...)
> >
> > Well, that's kind of difficult without using git for development work.
> > I can try to remember to name patches suitably, but that's
> > another manual step for me then
>
> Well, it's either an extra manual step for you, or an extra manual step
> for every person who reviews your code. You don't need to justify to me
> why you don't want to use git for development. However, it's not fair
> to externalize the cost of your development preferences to everybody else.
>
> When it's just one or two patches I'm willing to make some
> accommodation, but a series like this it's too much.
I don't use git either (I use guilt). My solution to this problem is to
`guilt push' all my patches, then export them back as patches from the
commits using `git format-patch'.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-21 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 9:25 [PATCH 00/11] assorted follow-ups to recent XSAs Jan Beulich
2017-06-21 9:30 ` [PATCH 01/11] public: adjust documentation following XSA-217 Jan Beulich
2017-06-21 11:26 ` Andrew Cooper
2017-06-21 15:44 ` George Dunlap
2017-06-21 15:54 ` Jan Beulich
2017-06-21 16:53 ` George Dunlap
2017-06-21 17:55 ` Stefano Stabellini [this message]
2017-06-22 6:59 ` Jan Beulich
2017-06-22 9:52 ` George Dunlap
2017-06-21 9:31 ` [PATCH 02/11] gnttab: remove redundant xenheap check from gnttab_transfer() Jan Beulich
2017-06-21 11:28 ` Andrew Cooper
2017-06-21 9:32 ` [PATCH 03/11] make steal_page() return a proper error value Jan Beulich
2017-06-21 11:39 ` Andrew Cooper
2017-06-22 10:01 ` Julien Grall
2017-06-21 9:33 ` [PATCH 04/11] domctl: restrict DOMCTL_set_target to HVM domains Jan Beulich
2017-06-21 11:41 ` Andrew Cooper
2017-06-21 9:34 ` [PATCH 05/11] evtchn: convert evtchn_port_is_*() to plain bool Jan Beulich
2017-06-21 11:46 ` Andrew Cooper
2017-06-21 9:35 ` [PATCH 06/11] ARM: simplify page type handling Jan Beulich
2017-06-21 23:53 ` Stefano Stabellini
2017-06-21 9:36 ` [PATCH 07/11] x86: fold identical error paths in xenmem_add_to_physmap_one() Jan Beulich
2017-06-21 11:53 ` Andrew Cooper
2017-06-21 9:36 ` [PATCH 08/11] gnttab: remove host map in the event of a grant_map failure Jan Beulich
2017-06-21 9:37 ` [PATCH 09/11] gnttab: avoid spurious maptrack handle allocation failures Jan Beulich
2017-06-21 12:02 ` Andrew Cooper
2017-06-21 12:19 ` Jan Beulich
2017-06-22 14:16 ` Jan Beulich
2017-06-21 9:38 ` [PATCH 10/11] gnttab: limit mapkind()'s iteration count Jan Beulich
2017-06-21 12:13 ` Andrew Cooper
2017-06-21 9:38 ` [PATCH 11/11] gnttab: drop useless locking Jan Beulich
2017-07-14 12:34 ` Ping: " Jan Beulich
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=alpine.DEB.2.10.1706211054070.12819@sstabellini-ThinkPad-X260 \
--to=sstabellini@kernel.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.