From: Erik Rull <spamfolder@rdsoftware.de>
To: Stefan Weil <sw@weilnetz.de>
Cc: Erik Rull <erik.rull@rdsoftware.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Posting a patch?
Date: Mon, 14 May 2012 23:06:31 +0200 [thread overview]
Message-ID: <4FB173D7.8050208@rdsoftware.de> (raw)
In-Reply-To: <4FB16B68.3040307@weilnetz.de>
Stefan Weil wrote:
> Am 14.05.2012 22:12, schrieb Erik Rull:
>> Hi all,
>>
>> is there a guideline or manual how to send a patch to the qemu mailing
>> list? It seems as if this can be done somehow automagically using the
>> local git repository, but I didn't find a tool to do that.
>>
>> Thanks!
>>
>> Best regards,
>>
>> Erik
>
> Hi Erik,
>
> if you use git for sending, you don't risk that your mailer destroys the
> format of your patch.
> I usually use these commands to send a single patch from the QEMU source
> directory:
>
> # Create the patch file (name depends on the subject line of your patch).
> git format-patch HEAD^
> # Check the patch (fix any issues which were found).
> scripts/checkpatch.pl 0001-*
> # Get the maintainer who is responsible (there is not always one).
> scripts/get_maintainer.pl 0001-*
> # Send the patch.
> git send-email --to qemu-devel@nongnu.org --to "n.n <address@domain>" 0001-*
>
> Please read also http://wiki.qemu.org/Contribute/SubmitAPatch.
>
> Regards,
>
> Stefan W.
>
Thanks!
So I started a git pull to get the latest master and as well a git reset
--hard to assert that there are no modifications remaining.
Then I modified the file ui/x_keymap.c and called then the
git format-patch HEAD^
But I get 3 patches that are definitively not related to my changes:
erik@debian:~/qemu-test/qemu$ git format-patch HEAD^
0001-coroutine-Fix-setup-of-sigaltstack-coroutines.patch
0002-qcow2-Don-t-ignore-failure-to-clear-autoclear-flags.patch
0003-qemu-img-Fix-segmentation-fault.patch
erik@debian:~/qemu-test/qemu$
Using git diff shows my real changes...
So I created a patch file called keymap.patch but git format-patch HEAD^
just ignores it..
Maybe I missed something important...
Best regards,
Erik
next prev parent reply other threads:[~2012-05-14 21:06 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
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 [this message]
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=4FB173D7.8050208@rdsoftware.de \
--to=spamfolder@rdsoftware.de \
--cc=erik.rull@rdsoftware.de \
--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 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.