From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: moving away from CVS
Date: Mon, 14 Aug 2006 07:38:57 +0200 [thread overview]
Message-ID: <87lkprzxji.fsf@xs4all.nl> (raw)
In-Reply-To: <1155510374.18244.17.camel@diesel> (Hollis Blanchard's message of "Sun, 13 Aug 2006 18:06:14 -0500")
Hollis Blanchard <hollis@penguinppc.org> writes:
> On Sun, 2006-08-13 at 22:08 +0200, Jeroen Dekkers wrote:
>>
>> I also think we should switch to a better VCS. I'm actually using bzr
>> myself. If anyone is interested, I've published my SoC branch and the
>> CVS on my homepage:
>> http://dekkers.cx/bzr/grub2
>> http://dekkers.cx/bzr/grub2-cvs
>>
>> My preference is bzr, but almost everything is better than cvs. I
>> would happily use svn, mercurial or darcs for example.
>
> I agree; I think there are far better replacements for CVS. Personally I
> would highly recommend mercurial, but I suppose everybody has their own
> preferences. I noticed that Savannah, where the GRUB tree is currently
> hosted, offers subversion support...
I like subversion because it solves most problems, while I do not have
to learn something new.
--
Marco
next prev parent reply other threads:[~2006-08-14 5:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 15:13 Support for reading LVM volumes Jeroen Dekkers
2006-08-13 16:49 ` Hollis Blanchard
2006-08-13 18:23 ` Jeroen Dekkers
2006-08-13 19:51 ` Hollis Blanchard
2006-08-13 20:08 ` Jeroen Dekkers
2006-08-13 23:06 ` moving away from CVS Hollis Blanchard
2006-08-14 5:38 ` Marco Gerards [this message]
2006-08-14 10:09 ` Johan Rydberg
2006-08-14 13:28 ` Marco Gerards
2006-08-15 12:24 ` Support for reading LVM volumes Yoshinori K. Okuji
2006-08-15 11:30 ` Jeroen Dekkers
2006-08-15 12:06 ` Marco Gerards
2006-08-15 12:48 ` Yoshinori K. Okuji
2006-08-15 21:16 ` Jeroen Dekkers
2006-09-03 13:16 ` Thomas Schwinge
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=87lkprzxji.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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.