From: "François Revol" <revol@free.fr>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU git tree is now activate
Date: Sat, 25 Apr 2009 21:36:53 +0200 CEST [thread overview]
Message-ID: <10554555517-BeMail@laptop> (raw)
In-Reply-To: <49F331F9.2030308@us.ibm.com>
> Riku Voipio wrote:
> > On Fri, Apr 24, 2009 at 04:58:09PM -0500, Anthony Liguori wrote:
> >
> >> I've disabled SVN although the project still seems to exist on the
> >> Savannah server. Please do not commit to this repository anymore.
> >>
> >
> > It seems the git commits don't get posted to this mailing list
> > anymore.
> > Is that the purpose? I think the svn commit messages were usefull.
> >
>
> They go to qemu-commits@nongnu.org now. The thinking is that it's
> easier for people interested in commits to subscribe to that list and
> filter those messages into the same bucket as qemu-devel than it is
> for
> folks that aren't interested in these messages to filter them out.
>
> I can certainly direct them to qemu-devel if there is agreement that
> that's where we want them to go.
It would likely be better to keep it separate for people who just want
to know about their few patches once in a while...
Btw, I'm still trying to find out which package to install for git in
apt...
git-core?
I suppose gitk would bring in the needed CLI tools too...
François.
next prev parent reply other threads:[~2009-04-25 19:36 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
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 [this message]
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=10554555517-BeMail@laptop \
--to=revol@free.fr \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).