qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae...


From: Luca
Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae...
Date: Mon, 17 Sep 2007 23:14:41 +0200

On 9/17/07, Andreas Färber <address@hidden> wrote:
>
> Am 17.09.2007 um 14:18 schrieb Christian MICHON:
>
> > On 9/17/07, Philip Boulain <address@hidden> wrote:
> >>>>>> DON'T DO THIS KIND OF COMMIT AGAIN, PLEASE.
> >>>>> if we were using git (but you can do it locally anyway), you
> >>>>> would not
> >>>>> have these conflicts problems...
> >>>> Maybe... but Savannah uses a CVS frontend, as far as I know...
> >>> Those are excuses.
> >>
> >> So is a "you should have used X" argument. It doesn't invalidate the
> >> point that the commit was disruptive, and merely acts as bait for the
> >> grand old "version repository" flamewar.*
> >>
> >
> > since I mentionned "you should have used Git", I'll repeat:
> > this commit was not disruptive to any of the Git users, and will
> > never be.
> >
> > Evolve, or prepare to be assimilated into the Collective...
>
> Both the qemu.org and the Savannah project page only mention CVS. If
> there are better ways to get the code then inform your users how to
> use that.

http://brick.kernel.dk/git/?p=qemu.git;a=summary
It's tracking QEMU CVS; you're right that it's not mentioned anywhere
on the site (AFAICS).
You can also DIY with git-cvsimport; see e.g.
http://chneukirchen.org/blog/archive/2006/04/tracking-the-ruby-cvs-with-git.html

Luca

reply via email to

[Prev in Thread] Current Thread [Next in Thread]