All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] updating git tree
Date: Tue, 28 Apr 2009 21:25:56 +0200 CEST	[thread overview]
Message-ID: <8110443000-BeMail@laptop> (raw)
In-Reply-To: <1E122AE2-0595-45D0-8F90-371328DCF060@web.de>

> > you can use:
> >
> > git diff > tmp.patch
> > patch -R -p1 < tmp.patch
> > git pull
> > patch -p1 < tmp.patch
>
> Or to stick with a `git` workflow, you can do:
>
> git commit -a -m "Description of local change"
> git pull

So, was it too hard to tell it in the first place ? ;)

Though it doesn't like me...
I have a file to remove, one to add, and I don't want to commit all the
changes at once...

I tried git commit -i (it wanted it) -m "Merge usb-wacom into usb-hid"
hw/usb-hid.c Makefile hw/usb-wacom.c

but it didn't like usb-wacom.c being already gone by git rm ...
+ this stupid thing commited the popenaudio.c I wanted to leave for
another commit despite not using -a...

Plus it used the local hostname to make my email in the commit, and I
couldn't find git-config as I saw it somewhere to change it...

This is beyond logic.
I thought it was supposed to be simpler but I'll have to git clone
again, apply each diff and commit them separately... :(

François.

  reply	other threads:[~2009-04-28 19:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  6:50 [Qemu-devel] updating git tree C.W. Betts
2009-04-28  6:50 ` C.W. Betts
2009-04-28  6:54   ` Laurent Desnogues
2009-04-28  7:21     ` Bartlomiej Celary
2009-04-28  8:49     ` Christoph Egger
2009-04-28  9:32       ` Kevin Wolf
2009-04-28  9:38       ` [Qemu-devel] " Jan Kiszka
2009-04-28  9:42         ` Laurent Desnogues
2009-04-28 10:04         ` Kevin Wolf
2009-04-28 10:20           ` Jan Kiszka
2009-04-28 10:28             ` Kevin Wolf
2009-04-28 10:48               ` Jan Kiszka
2009-04-28 10:58                 ` Kevin Wolf
2009-04-28 11:14                   ` Jan Kiszka
2009-04-28 11:15                 ` François Revol
2009-04-28 10:25           ` Gerd Hoffmann
2009-04-28 11:11       ` [Qemu-devel] " François Revol
2009-04-28 12:03         ` Laurent Desnogues
2009-04-28 12:57           ` François Revol
2009-04-28 13:10             ` Laurent Vivier
2009-04-28 13:49               ` François Revol
2009-04-28 13:58                 ` Kevin Wolf
2009-04-28 15:10                   ` Laurent Vivier
2009-04-28 15:22                     ` Kevin Wolf
2009-04-28 15:40                       ` Laurent Vivier
2009-04-28 16:51               ` Andreas Färber
2009-04-28 19:25                 ` François Revol [this message]
2009-04-28 19:49                   ` Andreas Färber
2009-04-28 20:17                     ` François Revol
2009-04-28 21:01                       ` François Revol
2009-04-29  7:54                         ` Markus Armbruster
2009-04-29  8:51                           ` François Revol
2009-04-29  9:22                             ` Markus Armbruster
2009-04-29  9:57                               ` François Revol
2009-04-29  7:44                       ` Markus Armbruster

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=8110443000-BeMail@laptop \
    --to=revol@free.fr \
    --cc=andreas.faerber@web.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 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.