From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vadim Evard <v.e.evard@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence pkg-config's check for curses
Date: Mon, 21 Jan 2013 11:54:46 +0100 [thread overview]
Message-ID: <20130121105446.GA10400@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <50FC6376.2050903@gmail.com>
On Mon, Jan 21, 2013 at 01:36:54AM +0400, Vadim Evard wrote:
> By the way (sorry if this was discussed before and is a strong
> decision) I'd say e-mail based workflow is of course very flexible -
> and very very novice-unfriendly. Dash, I had to learn git commands
> I'd never use in my usual workflow with local or Github repos. And,
> well, I was not very good with that. 10 ways with 10 options in
> each. You all saw my previous patch mail with "fubar" header and no
> signed-off-by string.
>
> Is there a reason you (team) don't use e.g. Github at least for
> trivial patches?
Yes, the email-based approach is the most flexible but also has a
learning curve. For one-time contributors it can seem like wasted
effort.
The QEMU community is familiar with the email-based workflow and has
customized it. One key idea is that all patches go through
qemu-devel@nongnu.org - even trivial patches are exposed to code review
from the whole community. A new vector for code submission still needs
to keep this property.
For another open source project that I'm involved in I have set up a
cronjob that sends GitHub pull requests to the project mailing list.
This way the mailing list still sees all patches before they get
committed. Replying to patches doesn't work though - you still need to
log into GitHub in order to send comments to the author. I can't ask
all QEMU developers to do that.
Any ideas how to make GitHub work with QEMU?
Stefan
next prev parent reply other threads:[~2013-01-21 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 13:48 [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence pkg-config's check for curses Vadim Evard
2013-01-18 14:06 ` Stefan Hajnoczi
2013-01-20 21:36 ` Vadim Evard
2013-01-21 10:54 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 23:52 [Qemu-devel] [Qemu-trivial] [PATCH] configure: silencing " Vadim Evard
2013-01-16 14:54 ` Anthony Liguori
2013-01-16 20:17 ` [Qemu-devel] [Qemu-trivial] [PATCH v2] configure: silence " Vadim Evard
2013-01-17 20:01 ` Anthony Liguori
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=20130121105446.GA10400@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=v.e.evard@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).