From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Jordan Justen (Intel address)" <jordan.l.justen@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
qemu devel list <qemu-devel@nongnu.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [Qemu-devel] why restrict pull reqs to signed tags?
Date: Wed, 9 Mar 2016 13:19:11 +0100 [thread overview]
Message-ID: <56E014BF.7060507@redhat.com> (raw)
In-Reply-To: <56E0136E.8050709@redhat.com>
On 09/03/2016 13:13, Laszlo Ersek wrote:
> David is proposing that direct pull requests be allowed on edk2-devel,
> immediately from contributors, so that the contributor may ask for
> his/her exact history to be preserved. I'm looking for examples: high
> profile projects that have adopted such a workflow *all the while*
> enforcing patch-wise reviews. Thus far I've come up empty.
Ironically, projects using github pull requests do this. They do code
review through the website and merge with a button. The resulting
history is non-linear.
Paolo
next prev parent reply other threads:[~2016-03-09 12:19 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 [this message]
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
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=56E014BF.7060507@redhat.com \
--to=pbonzini@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dwmw2@infradead.org \
--cc=jordan.l.justen@intel.com \
--cc=lersek@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.