From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
"Wieczorkiewicz, Pawel" <wipawel@amazon.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
"Tim \(Xen.org\)" <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
"Pohlack, Martin" <mpohlack@amazon.de>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
Julien Grall <julien.grall@arm.com>,
'Jan Beulich' <jbeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation
Date: Thu, 15 Aug 2019 19:59:28 +0100 [thread overview]
Message-ID: <7C16DC4F-18E5-4379-8A83-74DDA010F01C@gmail.com> (raw)
In-Reply-To: <bd7a904d-83dd-2499-28ea-0adb294587c8@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2821 bytes --]
> On 15 Aug 2019, at 17:29, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>
> On 15/08/2019 16:42, Wieczorkiewicz, Pawel wrote:
>> Thanks Julien. I will do that next time (unless you guys want me to
>> re-send all this ;-)).
>>
>> BTW, I also pushed my changes onto the xenbits server:
>> http://xenbits.xenproject.org/gitweb/?p=people/wipawel/livepatch-build-tools;a=summary
>> http://xenbits.xenproject.org/gitweb/?p=people/wipawel/xen;a=summary
>>
>> I hope that makes navigation and dealing with the swarm of patches a
>> bit easier.
>
> Please (re)send two patch series, one for Xen and one for build tools.
> Even for he subset you posted before, I can't figure out whether they're
> ok to push straight away, or need more review. This will be far easier
> to do in one single go (per repo).
>
> My workflow for series is something like this:
>
> First, confirm your git settings (details as appropriate)
>
> $ git config -l | grep sendemail
> sendemail.smtpserver= $SERVER
> sendemail.chainreplyto=false
> sendemail.to=Xen-devel <xen-devel@lists.xenproject.org>
> sendemail.from= $ME <$ME@example.com>
>
> Second, render the patch series:
>
> $ mkdir foo-v1
> $ cd foo-v1
> $ git format-patch master --cover-letter
> 0000-cover-letter.patch
> 0001- ....
> ....
>
> $ $EDITOR 0000-cover-letter.patch
>
> Fill in as appropriate. Provide a brief overview, note the subject of
> companion series, etc. I also include the union of all CC'd people in
> each patch just below the Subject: header which avoids having to
> manually specify them later. Be aware that it is strict about RFCs, so
> has to be Cc: and not CC:
>
> Third, double check everything:
>
> $ git send-email --dry-run *.patch
>
> Fourth, spam the list by dropping the --dry-run.
>
> Fifth, sit back and watch the reviews come in[1].
>
> ~Andrew
@Andrew: You just outlined what's in the wiki and what the add_maintainers tool does.
We should chat about the Cc: vs CC:
* I may need to fix the tool as it uses CC: when used with some options
@Pawel: I submitted
https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg01575.html <https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg01575.html>
https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg01581.html <https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg01581.html>
which once applied ensures that the tools can be used on the live patch build tools
I also added https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Using_add_maintainers.pl_.28or_get_maintainer.pl.29_from_outside_of_xen.git <https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#Using_add_maintainers.pl_.28or_get_maintainer.pl.29_from_outside_of_xen.git>
Lars
[-- Attachment #1.2: Type: text/html, Size: 4422 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-15 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 11:27 [Xen-devel] [PATCH lp-metadata 2/3] livepatch: Handle arbitrary size names with the list operation Pawel Wieczorkiewicz
2019-08-15 11:38 ` Julien Grall
2019-08-15 14:58 ` Lars Kurth
2019-08-15 15:19 ` Wieczorkiewicz, Pawel
2019-08-15 15:29 ` Julien Grall
2019-08-15 15:32 ` George Dunlap
2019-08-15 15:36 ` Julien Grall
2019-08-15 15:48 ` George Dunlap
2019-08-15 16:00 ` Julien Grall
2019-08-15 16:23 ` George Dunlap
2019-08-15 15:42 ` Wieczorkiewicz, Pawel
2019-08-15 16:29 ` Andrew Cooper
2019-08-15 18:59 ` Lars Kurth [this message]
2019-08-21 18:38 ` Konrad Rzeszutek Wilk
2019-08-15 15:33 ` Lars Kurth
2019-08-15 15:46 ` Lars Kurth
2019-08-15 15:58 ` Julien Grall
2019-08-15 16:17 ` Lars Kurth
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=7C16DC4F-18E5-4379-8A83-74DDA010F01C@gmail.com \
--to=lars.kurth.xen@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=mpohlack@amazon.de \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wipawel@amazon.de \
--cc=wl@xen.org \
--cc=xen-devel@lists.xen.org \
--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 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).