qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Posting a patch?
Date: Mon, 14 May 2012 23:11:10 +0200	[thread overview]
Message-ID: <4FB174EE.1050606@weilnetz.de> (raw)
In-Reply-To: <4FB173D7.8050208@rdsoftware.de>

Am 14.05.2012 23:06, schrieb Erik Rull:
>
> 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
>

You must commit your local change before you can format a patch.

Regards,

Stefan W.

      reply	other threads:[~2012-05-14 21:11 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
2012-05-14 21:11     ` Stefan Weil [this message]

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=4FB174EE.1050606@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=erik.rull@rdsoftware.de \
    --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 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).