From: Eric Blake <eblake@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Varad Gautam" <varadgautam@gmail.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] First Patch, Requesting Comments
Date: Mon, 18 Nov 2013 10:01:28 -0700 [thread overview]
Message-ID: <528A47E8.20804@redhat.com> (raw)
In-Reply-To: <528A4413.5020404@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
On 11/18/2013 09:45 AM, Andreas Färber wrote:
> Am 18.11.2013 16:59, schrieb Varad Gautam:
>>> To discuss the code you really should post the patch, I couldn't
>>> find any related code by your link.
>>
>> Hi! I had posted the patch onto the list.
>
> Unfortunately several copies of your mail arrived on the list today, and
> only one actually has the patch it talks about threaded to it. ;)
Often-times, this happens when a new contributor fails to realize that
the list is moderated, but that we will moderate non-subscriber's
messages through. What commonly happens is that a new contributor sends
a message, sees nothing on the archives, so they then subscribe, then
send again under the assumption that it would help; and sometimes even
send a third time when getting impatient that it hasn't shown up in list
archives. Then, a few hours later, when the moderator finally releases
the gates on the first-time post (a delay which happens whether you
posted as a subscriber or non-subscriber), all of the multiple pending
messages hit the list, making the new poster sound redundant.
Varad, as a new contributor, you are in a position to possibly help us:
what documentation pages did you read to learn where to post your
patches, so that we can try and modify those pages to give more hints to
help the next guy avoid the embarrassment of double posting?
>
> But welcome to the community, and you'll surely find out how to optimize
> your workflow for the second patch. :)
Indeed. And if you haven't already found it,
http://wiki.qemu.org/Contribute/SubmitAPatch is a great resource (and
again, knowing what pages you HAVE found may help us figure out if we
can tweak those pages to more prominently point to this page).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-11-18 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 13:49 [Qemu-devel] First Patch, Requesting Comments Varad Gautam
2013-11-18 15:45 ` Max Filippov
2013-11-18 15:59 ` [Qemu-devel] First Patch, Requesting Comments Varad Gautam
2013-11-18 16:45 ` Andreas Färber
2013-11-18 17:01 ` Eric Blake [this message]
2013-11-18 18:41 ` Varad Gautam
2013-11-18 19:01 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2013-11-18 14:00 Varad Gautam
2013-11-18 14:06 Varad Gautam
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=528A47E8.20804@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=varadgautam@gmail.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).