qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik Rull <erik.rull@rdsoftware.de>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] Posting a patch?
Date: Mon, 14 May 2012 23:10:08 +0200	[thread overview]
Message-ID: <4FB174B0.9080804@rdsoftware.de> (raw)
In-Reply-To: <4FB17352.1010901@redhat.com>

Eric Blake wrote:
> On 05/14/2012 02:58 PM, Anthony Liguori wrote:
>> You can also do:
>>
>> git send-email --to=qemu-devel@nongnu.org HEAD~1
>>
>> Which avoids any clutter.
>
> I also like to do:
>
> git config sendemail.to=qemu-devel@nongnu.org
>
> so I don't have to remember to use --to every time.
>
> 'git send-email --cover-letter' gives a nicer cover letter than 'git
> send-email --compose'; it really bothers me that 'git send-email --help'
> fails to mention that send-email also understands all options of
> format-patch.
>

Thanks for your help. I need to figure out first, why git detects other 
changes than mine for posting despite a git checkout master, git pull, git 
reset --hard and make distclean.
(See previous email)

Best regards,

Erik

  reply	other threads:[~2012-05-14 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 20:12 [Qemu-devel] Posting a patch? Erik Rull
2012-05-14 20:30 ` Stefan Weil
2012-05-14 20:53   ` Peter Maydell
2012-05-14 20:58     ` Anthony Liguori
2012-05-14 21:04       ` Eric Blake
2012-05-14 21:10         ` Erik Rull [this message]
2012-05-14 21:20           ` Stefan Weil
2012-05-14 21:29             ` Erik Rull
2012-05-14 21:08       ` Stefan Weil
2012-05-14 21:14     ` Stefan Weil
2012-05-15 10:18       ` Peter Maydell
2012-05-14 21:06   ` Erik Rull
2012-05-14 21:11     ` Stefan Weil

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=4FB174B0.9080804@rdsoftware.de \
    --to=erik.rull@rdsoftware.de \
    --cc=anthony@codemonkey.ws \
    --cc=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).