qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luca <kronos.it@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae...
Date: Mon, 17 Sep 2007 23:14:41 +0200	[thread overview]
Message-ID: <68676e00709171414j4bf64c83p8a6a01897708f1cb@mail.gmail.com> (raw)
In-Reply-To: <F09F687E-169F-4E93-8CAC-912DA57CC577@web.de>

On 9/17/07, Andreas Färber <andreas.faerber@web.de> wrote:
>
> Am 17.09.2007 um 14:18 schrieb Christian MICHON:
>
> > On 9/17/07, Philip Boulain <prb@ecs.soton.ac.uk> 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	other threads:[~2007-09-17 21:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 21:08 [Qemu-devel] qemu Changelog Makefile Makefile.target TODO ae Thiemo Seufer
2007-09-17  8:08 ` J. Mayer
2007-09-17  8:27   ` Christian MICHON
2007-09-17  9:42     ` J. Mayer
2007-09-17 10:00       ` Johannes Schindelin
2007-09-17 11:19         ` Philip Boulain
2007-09-17 12:18           ` Christian MICHON
2007-09-17 20:59             ` Andreas Färber
2007-09-17 21:14               ` Luca [this message]
2007-09-17 21:46                 ` J. Mayer
2007-09-17 22:02                   ` Luca
2007-09-18 13:21                   ` Thiemo Seufer
2007-09-17 21:30               ` Christian MICHON
2007-09-17 22:47               ` Johannes Schindelin
2007-09-18 16:20                 ` Andreas Färber
2007-09-17  9:21   ` Johannes Schindelin
2007-09-17 14:52     ` M. Warner Losh
2007-09-17 13:52   ` Thiemo Seufer
  -- strict thread matches above, loose matches on Subject: below --
2007-09-17 23:56 Ben Taylor
2007-09-18 12:49 ` Philip Boulain
2007-09-18 17:05   ` Stefan Weil

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=68676e00709171414j4bf64c83p8a6a01897708f1cb@mail.gmail.com \
    --to=kronos.it@gmail.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).