From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
qemu devel list <qemu-devel@nongnu.org>,
"Jordan Justen (Intel address)" <jordan.l.justen@intel.com>
Subject: Re: [Qemu-devel] why restrict pull reqs to signed tags?
Date: Wed, 9 Mar 2016 14:14:09 +0100 [thread overview]
Message-ID: <56E021A1.4060108@redhat.com> (raw)
In-Reply-To: <CAFEAcA-yZg+YYTENcN6t2YJ_vomp9Nve2ax8YHbaFpidh-a5kg@mail.gmail.com>
On 03/09/16 13:44, Peter Maydell wrote:
> On 9 March 2016 at 19:40, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> Laszlo is going to shoot me for saying this, but as a compromise
>> between the Windows crowd in the Intel firmware team and the more
>> Linux/open source oriented people on the opposite side, using github
>> does not sound like an entirely unreasonable compromise. At least it
>> means no emails anymore with garbled patches and 300 character lines
>> in the commit log
>
> By the way, why are you all discussing the EDK2 patch workflow
> proposals on qemu-devel and not on an EDK mailing list?
Sorry, that's where we started, and the rest of the discussion should
happen there; I agree. The reason for coming here was that we ended up
questioning / re-examining the practices we had taken as examples: QEMU,
Linux. I needed some info from the source, and I wanted to allow anyone
on qemu-devel to chime in. (This is why I didn't ask only you
personally, edk2-devel CC'd.)
Thanks
Laszlo
next prev parent reply other threads:[~2016-03-09 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 10:20 [Qemu-devel] why restrict pull reqs to signed tags? Laszlo Ersek
2016-03-09 11:33 ` Paolo Bonzini
2016-03-09 11:35 ` Peter Maydell
2016-03-09 12:13 ` Laszlo Ersek
2016-03-09 12:19 ` Paolo Bonzini
2016-03-09 12:31 ` Laszlo Ersek
2016-03-09 12:33 ` Paolo Bonzini
2016-03-09 12:38 ` David Woodhouse
2016-03-09 12:40 ` Ard Biesheuvel
2016-03-09 12:44 ` Peter Maydell
2016-03-09 13:14 ` Laszlo Ersek [this message]
2016-03-09 12:34 ` David Woodhouse
2016-03-09 12:42 ` Peter Maydell
2016-03-09 13:09 ` David Woodhouse
2016-03-09 13:27 ` Peter Maydell
2016-03-09 14:13 ` David Woodhouse
2016-03-09 14:41 ` Laszlo Ersek
2016-03-10 8:21 ` David Woodhouse
2016-03-10 8:52 ` Markus Armbruster
2016-03-10 10:34 ` David Woodhouse
2016-03-10 12:38 ` Laszlo Ersek
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=56E021A1.4060108@redhat.com \
--to=lersek@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dwmw2@infradead.org \
--cc=jordan.l.justen@intel.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.