All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: "François Revol" <revol@free.fr>
Cc: andreas.faerber@web.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] updating git tree
Date: Tue, 28 Apr 2009 23:01:36 +0200 CEST	[thread overview]
Message-ID: <13850618085-BeMail@laptop> (raw)
In-Reply-To: <11194473229-BeMail@laptop>

> >
> > To commit individual files, use `git add file1.c`, then `git
> > commit`
> > without -a.
> > You can check `git status` for what'll get committed.
>
> That I guessed, but there is no way to forbid commiting deleted files
> at once...
>

So here is what I've did, FWIW:

svn diff > svn-popenaudio.diff
svn diff > svn-hid.diff
# vi both to only keep related changes
cd ..

git clone ...

git apply -p0 < ../svn-hid.diff
git rm hw/usb-wacom.c
git commit -a -m "Merge usb-wacom.c into usb-hid.c"
# argh, git status sayw hw/usb-wacom.c is still here...
rm hw/usb-wacom.c

# generate a diff...
git-format-patch -s origin
# of course it outputs a stupid mbox format which isn't used everywhere
# so I must strip the headers if I just need the real patch
(overengineering)
for f in 0???-*; do sed '1,/^$/d' -i "$f"; done

git apply -p0 < ../svn-popenaudio.diff
# now I should probably finish it first as I don't know how to generate
a single merged patch from multiple commits...
#git add audio/popenaudio.c
#git commit -a -m "Start of popen(3) audio output"

François.

  reply	other threads:[~2009-04-28 21:01 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
2009-04-28 19:49                   ` Andreas Färber
2009-04-28 20:17                     ` François Revol
2009-04-28 21:01                       ` François Revol [this message]
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=13850618085-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.