From: "François Revol" <revol@free.fr>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: blauwirbel@gmail.com, edgar.iglesias@gmail.com,
paul@codesourcery.com, aurelien@aurel32.net,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] REMINDER: QEMU SVN => GIT switch today at 5pm CST
Date: Fri, 24 Apr 2009 19:18:00 +0200 CEST [thread overview]
Message-ID: <10208245490-BeMail@laptop> (raw)
In-Reply-To: <49F1EFFA.40100@us.ibm.com>
> > svn up + vim + svn resolved :D
>
> So all your patches are maintained as changed to the currently
> working
> directory in svn??
Not like there are too many, just this usb-hid one isn't yet commited.
And I started a popen() audio out but didn't finish.
It works fine usually, plus I have many other things checked out from
cvs or other I need to maintain anyway... mostly ffmpeg because they
think "porting" means porting the OS to the app and so are rejecting
some obvious stuff.
> You should really invest in learning git or mercurial. It will make
> your life a lot easier. It's pretty trivial to create a local hg
> mirror
> from a git tree.
At least hg was easy to port to BeOS (still had to change some lines
due to people using #!/usr/bin/env python to locate python and just
moving the issue to env itself...)
Still I don't like much those hashes around, and I always need to dig
the gitweb 10min just to get to the source tree...
> In the very least, you should look at something like quilt. Then you
> can avoid ever learning about git if that's what you wish.
Maybe, I'll queue it on my TODO list.
Btw, the CC field is getting crowded... when I talk bout misconfigured
lists...
François.
next prev parent reply other threads:[~2009-04-24 17:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 16:37 [Qemu-devel] REMINDER: QEMU SVN => GIT switch today at 5pm CST Anthony Liguori
2009-04-24 16:42 ` François Revol
2009-04-24 16:50 ` Anthony Liguori
2009-04-24 16:56 ` François Revol
2009-04-24 16:59 ` Anthony Liguori
2009-04-24 17:18 ` François Revol [this message]
2009-04-24 17:56 ` Lennart Sorensen
2009-04-24 21:10 ` Rob Landley
2009-04-25 3:11 ` François Revol
2009-04-25 3:08 ` François Revol
2009-04-27 13:06 ` Lennart Sorensen
2009-04-27 13:20 ` Laurent Desnogues
2009-04-27 13:56 ` M. Warner Losh
2009-04-27 14:16 ` Lennart Sorensen
2009-04-27 14:53 ` John Haxby
2009-04-27 17:16 ` Lennart Sorensen
2009-04-27 17:35 ` François Revol
2009-04-27 18:14 ` Lennart Sorensen
2009-04-27 18:18 ` Lennart Sorensen
2009-04-27 19:27 ` Riku Voipio
2009-04-27 20:37 ` Jamie Lokier
2009-04-27 22:54 ` Lennart Sorensen
2009-04-24 23:51 ` Johannes Schindelin
2009-04-25 3:29 ` François Revol
2009-04-25 9:12 ` Johannes Schindelin
2009-04-24 21:02 ` Rob Landley
2009-04-24 21:06 ` Anthony Liguori
2009-04-24 21:58 ` [Qemu-devel] QEMU git tree is now activate Anthony Liguori
2009-04-25 15:26 ` Riku Voipio
2009-04-25 15:53 ` Anthony Liguori
2009-04-25 17:11 ` Aurelien Jarno
2009-04-25 17:45 ` Edgar E. Iglesias
2009-04-27 18:36 ` Stefan Weil
2009-04-27 18:38 ` Anthony Liguori
2009-04-25 18:04 ` Stefan Weil
2009-04-25 19:17 ` Riku Voipio
2009-04-25 19:36 ` François Revol
2009-04-27 16:33 ` [Qemu-devel] " Consul
2009-04-27 18:41 ` Jan Kiszka
2009-04-27 18:47 ` [Qemu-devel] " Christoph Hellwig
2009-04-27 21:18 ` Anthony Liguori
2009-04-27 21:20 ` Laurent Desnogues
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=10208245490-BeMail@laptop \
--to=revol@free.fr \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=paul@codesourcery.com \
--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).