From: Ian Campbell <ian.campbell@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Pry Mar <pryorm09@gmail.com>,
cfergeau@redhat.com
Subject: Re: [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0
Date: Mon, 8 Feb 2016 09:58:23 +0000 [thread overview]
Message-ID: <1454925503.8672.120.camel@citrix.com> (raw)
In-Reply-To: <CAB=NE6XbV7j8UzUgVTSRpfYTB2TbqJ4PCtYOvJ4on4dEnU4b9A@mail.gmail.com>
On Fri, 2016-02-05 at 17:48 -0800, Luis R. Rodriguez wrote:
> What's up folks? How can this process be made smoother, did I do
> something wrong, what can I do to help better?
When you first sent this series to Jan + me not copying the list you were
asked to send to the list _and_ to CC the appropriate maintainers.
When you resent you only added the xen-devel CC without adjusting the CC.
Jan pointed this out to you (as a subsequent reply to the original private
thread) and so I archived both threads in anticipation of a corrected
series being resent in the not to distant future.
CCing maintainers is part of the Xen workflow just as it is with Linux, I
don't think you would expect to send a random selection of e.g. arch/x86
and drivers/net fixes to Linus+GregKH and have anything useful happen to
them.
If you were a newbie to this sort of thing I would probably have kept a
closer eye out for a v3 and given you some guidance if it didn't
materialise in a week or two but I didn't think it would be necessary in
your case since I know you are familiar with this sort of thing from the
Linux world and your previous contributions to Xen.
FWIW I would also suggest sending fixes to different components (qemu-xen,
qemu-xentraditional, xen.git, mini-os.git) as different series, lest
someone read patch #1 and assume the whole series is against that component
rather than something they maintain.
And BTW when we say to copy the maintainers we mean the person/people
responsible for the component in Xen, not the upstream maintainers, e.g.
Stefano for qemu-xen not Peter Maydell. The xen.git MAINTAINERS file lists
the right people.
Ian.
> What can you do to help
> ensure these types of things don't fall through the cracks.
>
> [0] http://comments.gmane.org/gmane.comp.emulators.xen.devel/264183
>
> Luis
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-08 9:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 17:47 [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0 Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 1/9] Revert "Use the extra stack for 16bit USB and PS2 keyboard/mouse commands." Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 2/9] Use gnutls_priority_set_direct() to deprecate gnutls_*_set() Luis R. Rodriguez
2015-11-25 14:53 ` Konrad Rzeszutek Wilk
2015-11-25 19:36 ` [Xen-devel] " Luis R. Rodriguez
2015-11-25 20:44 ` Konrad Rzeszutek Wilk
2016-02-06 1:44 ` [Xen-devel] " Luis R. Rodriguez
2016-02-06 3:45 ` Konrad Rzeszutek Wilk
2016-02-06 4:03 ` Luis R. Rodriguez
2016-02-06 4:12 ` Konrad Rzeszutek Wilk
2016-02-06 4:36 ` Luis R. Rodriguez
2016-02-06 20:18 ` Doug Goldstein
2016-02-09 10:54 ` Jan Beulich
2016-02-09 15:46 ` [Xen-devel] " Luis R. Rodriguez
2016-02-09 16:06 ` Jan Beulich
2016-02-09 16:36 ` Olaf Hering
2016-02-09 16:42 ` [Xen-devel] " Luis R. Rodriguez
2016-02-09 18:23 ` Olaf Hering
2016-02-10 3:04 ` [Xen-devel] " Luis R. Rodriguez
2016-02-10 9:46 ` Ian Campbell
2016-02-10 15:41 ` [Xen-devel] " Luis R. Rodriguez
2016-02-10 15:44 ` Olaf Hering
2016-02-10 15:55 ` [Xen-devel] " Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 3/9] hw/usb-net.c: fix state check Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 4/9] qemu-xen-dir: spice: remove spice-experimental.h include Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 5/9] qemu-xen-dir: virtio-rng: fix check for period_ms validity Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 6/9] mini-os: fix linker warning with app.lds Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 7/9] stubdom: fix unfound libgmp library issues Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 8/9] vtpm: fix vtpmblk.c compilation warning Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 9/9] vtpm: guard against redefining TPM_VENDOR_COMMAND Luis R. Rodriguez
2016-02-06 1:48 ` [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0 Luis R. Rodriguez
2016-02-06 3:52 ` Konrad Rzeszutek Wilk
2016-02-06 4:07 ` Luis R. Rodriguez
2016-02-06 20:22 ` Doug Goldstein
2016-02-07 5:34 ` Fengguang Wu
2016-02-08 9:58 ` Ian Campbell [this message]
2016-02-09 15:56 ` Luis R. Rodriguez
2016-02-09 16:26 ` Ian Campbell
2016-02-09 16:39 ` Luis R. Rodriguez
2016-02-10 9:34 ` Ian Campbell
2016-02-09 8:08 ` Jan Beulich
2016-02-09 16:09 ` Luis R. Rodriguez
2016-02-09 16:22 ` Ian Campbell
2016-02-09 16:30 ` Luis R. Rodriguez
2016-02-09 16:39 ` Ian Campbell
2016-02-09 16:53 ` Luis R. Rodriguez
2016-02-10 5:21 ` Luis R. Rodriguez
2016-02-10 9:38 ` Ian Campbell
2016-02-10 5:44 ` Luis R. Rodriguez
2016-02-10 9:47 ` Ian Campbell
2016-02-11 8:08 ` Olaf Hering
2016-02-10 0:24 ` Dario Faggioli
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=1454925503.8672.120.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=cfergeau@redhat.com \
--cc=mcgrof@suse.com \
--cc=pryorm09@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.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 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).