All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Moving to another SCM
Date: Tue, 22 May 2007 20:52:58 +0200	[thread overview]
Message-ID: <20070522185258.GA12275@aragorn> (raw)
In-Reply-To: <87ejlat420.fsf@lab.ossystems.com.br>

On Mon, May 21, 2007 at 03:38:47PM -0300, Otavio Salvador wrote:
> Hello,
> 
> I'd like to ask if GRUB is planning to move to another SCM?
> 
> I've been using GIT for a while and it looks great for the kinda of
> work done at GRUB since there're a lot of people working together and
> sometimes a feature need some time to get mature enough to be merged
> in and this fits very well how GIT is used.
> 
> There's any plans for it? What's the options that current developers
> have in mind?

I'm not very familiar with GIT, although my understanding is that it has
advantages related to branching and also a nice regression test feature.

Also, for distributors for Debian, it seems to be useful since the Debian
package can be considered a branch from official GRUB in the SCM itself.

Anyway, I find CVS very awkward to work with.  I tend to agree with Otavio
that a change would be a good thing (be it to git, svn...).

Just my 0.02.

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



  reply	other threads:[~2007-05-22 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 18:38 Moving to another SCM Otavio Salvador
2007-05-22 18:52 ` Robert Millan [this message]
2007-05-22 21:58   ` Jeroen Dekkers
2007-05-27 12:13     ` Thomas Schwinge
2007-05-27 13:29       ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2007-06-18 12:39 Sam Morris

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=20070522185258.GA12275@aragorn \
    --to=rmh@aybabtu.com \
    --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.