qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Chad Joan <chadjoan@gmail.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fix build break during configuration on musl-libc based Linux systems.
Date: Fri, 17 Feb 2017 14:43:27 +0800	[thread overview]
Message-ID: <20170217064327.GB21716@lemon.lan> (raw)
In-Reply-To: <CABHMSTUsZy0u4b1b84YC5CgafKvD-Zms5dCQ=31+XnQphUQxLA@mail.gmail.com>

On Thu, 02/16 12:47, Chad Joan wrote:
> I am glad others are chiming in and might provide better solutions.
> 
> Honestly, following the instructions at
> http://wiki.qemu-project.org/Contribute/SubmitAPatch to-the-letter is quite
> daunting to me, just to get one line of code changed.  It might help if
> that page had some kind of dead-simple example for trivial patches;
> something like:
> $ cd <QEMU directory>
> $ git format-patch blah blah blah
> $ maybe-some-other-command
> $ # Now copy the contents of file xyz.patch into your email client and send
> to qemu-devel@nongnu.org and qemu-trivial@nongnu.org

Makes sense in general except for the sending part - email clients tend to
damage the patch when you copy and paste by wrapping long lines or messing up
other things. But your point is taken, we should make the first (or a one-shot)
contribution as easy as possible.

Fam

  reply	other threads:[~2017-02-17  6:43 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 [this message]
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
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=20170217064327.GB21716@lemon.lan \
    --to=famz@redhat.com \
    --cc=chadjoan@gmail.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).