From: Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] RFC RFC
Date: Wed, 18 Feb 2015 11:10:50 +0300 [thread overview]
Message-ID: <54E4490A.2030706@parallels.com> (raw)
Hi
Can anybody explain what the reasons, politics and consequences of
adding RFC into patch header in this mailing list? I think, it is not
worth to add this information to
http://wiki.qemu.org/Contribute/SubmitAPatch
--
Best regards,
Vladimir
next reply other threads:[~2015-02-18 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 8:10 Vladimir Sementsov-Ogievskiy [this message]
2015-02-18 8:37 ` [Qemu-devel] RFC RFC Peter Maydell
2015-02-18 14:01 ` Eric Blake
2015-02-18 14:10 ` Vladimir Sementsov-Ogievskiy
2015-02-18 14:32 ` Max Filippov
2015-02-18 14:54 ` Vladimir Sementsov-Ogievskiy
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=54E4490A.2030706@parallels.com \
--to=vsementsov@parallels.com \
--cc=qemu-devel@nongnu.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.