From: Anthony Liguori <anthony@codemonkey.ws>
To: malc <av1474@comtv.ru>, Paul Brook <paul@codesourcery.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Commit 99a0949 (using the mailing list)
Date: Thu, 01 Oct 2009 16:17:36 -0500 [thread overview]
Message-ID: <4AC51C70.2030006@codemonkey.ws> (raw)
I've reverted 99a0949. It's not necessarily a bad change to make but
something that's so invasive as that absolutely requires some discussion
before hand. Avoiding "bike-shedding" is not a valid argument for
avoiding the list.
For instance, I find the naming to be truly awful and would have liked
some discussion on a more reasonable naming convention.
I have a very large set of patches in my queue (over 200) that I'm
testing and trying to commit. A lot of other people do. If we're going
to make a change like this, it's very important to coordinate with
people so that they can flush their queues and avoid massive merge
head-ache.
Regards,
Anthony Liguori
next reply other threads:[~2009-10-01 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 21:17 Anthony Liguori [this message]
2009-10-01 22:06 ` [Qemu-devel] Re: Commit 99a0949 (using the mailing list) Anthony Liguori
2009-10-02 15:53 ` Blue Swirl
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=4AC51C70.2030006@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=av1474@comtv.ru \
--cc=paul@codesourcery.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.