From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Amit Shah <amit.shah@redhat.com>,
Mark McLoughlin <markmc@redhat.com>,
Bernhard Kauer <kauer@os.inf.tu-dresden.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained?
Date: Sun, 13 Sep 2009 18:44:36 +0300 [thread overview]
Message-ID: <4AAD1364.40801@redhat.com> (raw)
In-Reply-To: <f43fc5580909112255o5a2abf73rf4b990e5ba6471d1@mail.gmail.com>
On 09/12/2009 08:55 AM, Blue Swirl wrote:
> We had a discussion about this earlier this year:
> http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg01184.html
>
> Since that we have switched to git, so a lot of it could be
> simplified. Instead of the lengthy formatting specification, we could
> just require that the patch should apply with "git-am" to git HEAD
> without any editing, merging or even apply.whitespace=fix.
>
That doesn't tell people what information to include, and if they don't
care how the log looks like, they'll do the minimum amount of work to
make git am like it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-13 15:44 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 7:49 [Qemu-devel] [PATCH] [RESEND] RTC polling mode broken Bernhard Kauer
2009-09-09 12:18 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Bernhard Kauer
2009-09-09 12:23 ` Amit Shah
2009-09-09 12:58 ` Bernhard Kauer
2009-09-09 12:25 ` Kevin Wolf
2009-09-09 13:00 ` Anthony Liguori
2009-09-09 13:26 ` Gleb Natapov
2009-09-09 13:45 ` Anthony Liguori
2009-09-09 14:31 ` Avi Kivity
2009-09-09 13:34 ` Bernhard Kauer
2009-09-10 7:03 ` Amit Shah
2009-09-10 7:56 ` Reimar Döffinger
2009-09-10 10:08 ` Amit Shah
2009-09-10 11:47 ` Luiz Capitulino
2009-09-10 12:01 ` [Qemu-devel] QEMU patch management Amit Shah
2009-09-10 12:29 ` [Qemu-devel] " Luiz Capitulino
2009-09-10 12:51 ` Reimar Döffinger
2009-09-10 13:11 ` Luiz Capitulino
2009-09-10 17:24 ` Reimar Döffinger
2009-09-10 13:58 ` [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Anthony Liguori
2009-09-10 13:56 ` Anthony Liguori
2009-09-10 14:04 ` Amit Shah
2009-09-10 14:12 ` Anthony Liguori
2009-09-10 15:15 ` Amit Shah
2009-09-10 14:38 ` Avi Kivity
2009-09-10 15:54 ` Anthony Liguori
2009-09-10 16:09 ` Avi Kivity
2009-09-10 16:22 ` Anthony Liguori
2009-09-10 16:35 ` Avi Kivity
2009-09-10 16:38 ` Anthony Liguori
2009-09-10 16:46 ` Avi Kivity
2009-09-10 17:19 ` Reimar Döffinger
2009-09-11 12:39 ` Amit Shah
2009-09-12 5:55 ` Blue Swirl
2009-09-13 15:44 ` Avi Kivity [this message]
2009-09-13 16:30 ` Blue Swirl
2009-09-11 7:06 ` Gerd Hoffmann
2009-09-10 18:29 ` Mark McLoughlin
2009-09-10 18:40 ` Avi Kivity
2009-09-10 19:31 ` Anthony Liguori
2009-09-13 15:49 ` Avi Kivity
2009-09-10 20:36 ` Mark McLoughlin
2009-09-13 16:19 ` Avi Kivity
2009-09-14 7:49 ` Mark McLoughlin
2009-09-14 7:59 ` Avi Kivity
2009-09-10 18:59 ` Reimar Döffinger
2009-09-10 16:05 ` Anthony Liguori
2009-09-10 16:14 ` Avi Kivity
2009-09-11 9:16 ` [Qemu-devel] commit e09a5267 (was: [PATCH] [RESEND2] Qemu unmaintained?) Jan Kiszka
2009-09-11 12:56 ` [Qemu-devel] Re: commit e09a5267 Anthony Liguori
2009-09-11 13:04 ` Jan Kiszka
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=4AAD1364.40801@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kauer@os.inf.tu-dresden.de \
--cc=markmc@redhat.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 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).