From: Paolo Bonzini <pbonzini@redhat.com>
To: Chad Joan <chadjoan@gmail.com>, Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Fam Zheng <famz@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Fix build break during configuration on musl-libc based Linux systems.
Date: Fri, 17 Feb 2017 17:57:14 +0100 [thread overview]
Message-ID: <f42b803f-ba9e-fe14-a085-2023ac062c1c@redhat.com> (raw)
In-Reply-To: <CABHMSTWN2KdAXDjEEbyWio6rNM2FuDk_NUj40mFW0HdyZFu68g@mail.gmail.com>
On 17/02/2017 17:54, Chad Joan wrote:
> Regarding the signature: IIRC, setting up certificates on a machine
> using gpg can be quite time consuming and learning-intensive if you've
> never needed to do it before. Having that example will go a long way to
> help with this. There is still a possible pain-point: you might write
> one line of git code in the example, and it is easy for you due to your
> workflow, but it could be hours of fiddling for someone who has never
> done it before. If I'm wrong, show me (the hypothetical reader) how
> easy it is ;) If I'm right (and that would be unfortunate, in this
> case), then it might be helpful if you politely ask the reader to spend
> time X amount of time on it (establish accurate expectations) and then
> provide a link to the most helpful how-to article you can find on the
> subject.
GPG signing is not needed. All you need is "git commit -s".
Adding "Signed-off-by: Chad Joan <chadjoan@gmail.com>" basically is a
way to tell us "I understand I'm contributing this under the GNU GPL or
a compatible license". It's not a cryptographic signature.
Paolo
next prev parent reply other threads:[~2017-02-17 16:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 16:30 [Qemu-devel] Fix build break during configuration on musl-libc based Linux systems Chad Joan
2017-02-16 16:58 ` Paolo Bonzini
2017-02-16 17:23 ` Laszlo Ersek
2017-02-16 17:47 ` Chad Joan
2017-02-17 6:43 ` Fam Zheng
2017-02-17 9:23 ` Laszlo Ersek
2017-02-17 10:11 ` Fam Zheng
2017-02-17 9:28 ` Peter Maydell
2017-02-17 15:34 ` Eric Blake
2017-02-17 16:54 ` Chad Joan
2017-02-17 16:56 ` Peter Maydell
2017-02-17 16:57 ` Paolo Bonzini [this message]
2017-02-17 17:07 ` Chad Joan
2017-02-17 17:15 ` Peter Maydell
2017-02-19 7:22 ` Chad Joan
2017-02-19 12:12 ` Peter Maydell
2017-02-21 2:53 ` Eric Blake
2017-02-17 17:17 ` Eric Blake
2017-02-19 7:02 ` Chad Joan
2017-02-21 3:02 ` Eric Blake
2017-02-21 9:41 ` Markus Armbruster
2017-02-21 9:58 ` Peter Maydell
2017-02-17 18:13 ` John Snow
2017-02-17 8:45 ` Paolo Bonzini
2017-02-17 8:56 ` Paolo Bonzini
2017-02-17 9:17 ` Laszlo Ersek
2017-02-17 11:11 ` Paolo Bonzini
2017-02-17 11:43 ` Chad Joan
2017-02-17 10:18 ` Peter Maydell
2017-02-17 11:20 ` Paolo Bonzini
2017-02-17 16:57 ` Peter Maydell
2017-04-06 18:15 ` Rainer Müller
2017-04-06 18:36 ` Peter Maydell
2017-06-02 13:58 ` Peter Maydell
2017-02-16 16:59 ` Eric Blake
2017-02-16 17:05 ` Peter Maydell
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=f42b803f-ba9e-fe14-a085-2023ac062c1c@redhat.com \
--to=pbonzini@redhat.com \
--cc=chadjoan@gmail.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).