All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: CVS (Re: Redefining GRUB_MOD_GAP in init.c)
Date: Tue, 29 Jan 2008 12:15:41 +0100	[thread overview]
Message-ID: <87tzkwanmq.fsf@xs4all.nl> (raw)
In-Reply-To: <20080129092754.GA31098@thorin> (Robert Millan's message of "Tue,  29 Jan 2008 10:27:54 +0100")

Robert Millan <rmh@aybabtu.com> writes:

> On Tue, Jan 29, 2008 at 10:21:59AM +0100, Marco Gerards wrote:
>> Robert Millan <rmh@aybabtu.com> writes:
>> 
>> > On Tue, Jan 29, 2008 at 09:36:41AM +0100, Marco Gerards wrote:
>> >> >
>> >> > Maybe it's time we move out those generic files under powerpc directory.  I
>> >> > propose moving the following:
>> >> >
>> >> > kern/powerpc/ieee1275/init.c
>> >> > kern/powerpc/ieee1275/cmain.c
>> >> > kern/powerpc/ieee1275/openfw.c
>> >> > loader/powerpc/ieee1275/multiboot2.c
>> >> 
>> >> Move it where?
>> >
>> > To s,powerpc/,,g
>> 
>> Fine for me...
>> 
>> It would be nice if we could switch to SVN or so soon.  SVN is
>> available on savannah and works almost the same as CVS.  I know there
>> are better systems to work with, but this is a no brainer I hope.
>> Moving files is no fun with CVS :-(
>
> I thought SVN wasn't (properly) supported by Savannah.

I am not sure: http://savannah.gnu.org/svn/?group=phpgroupware

They seem to use it...

>> What was the outcome of the previous discussions on this?  All these
>> threads explode with mails on which system is the best, because of
>> that I ignore the thread and nothing happens... :-)
>
> Some people wanted GIT, and Okuji objected, following a long, boring discussion
> about the advantages and disadvantages of GIT.

Yes, other people want bzr, others want bzr, etc, etc.  I do not
care.  This way we never switch, which is even worse.

> I personaly think we should just ditch CVS, because CVS has these annoying
> limitations, but not try to do something fancy.  SVN is the logical
> evolution of CVS, so why not just do that.

That's exactly what I was thinking ;-).  I was bothered by the
limitation.  And that we cannot discuss changing to svn first :-)

So what now?

> We can always switch to GIT in the future if/when everybody agrees.

Right!

--
Marco




  reply	other threads:[~2008-01-29 11:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  3:25 Redefining GRUB_MOD_GAP in init.c Pavel Roskin
2008-01-28  9:09 ` Robert Millan
2008-01-28  9:30   ` GRUB_MOD_GAP for non-ieee1275 ELF platforms Robert Millan
2008-01-28 13:44     ` Pavel Roskin
2008-01-28 16:29       ` Robert Millan
2008-01-28 16:34         ` Pavel Roskin
2008-01-28 16:57           ` Robert Millan
2008-01-29  8:38         ` Marco Gerards
2008-01-29  9:06           ` Robert Millan
2008-01-29  9:32             ` Marco Gerards
2008-01-29 10:04               ` Robert Millan
2008-01-30 21:42           ` Pavel Roskin
2008-01-30 22:03             ` Robert Millan
2008-01-30 22:15               ` Pavel Roskin
2008-01-30 22:26                 ` Robert Millan
2008-01-30 22:48                   ` Pavel Roskin
2008-01-31  8:48                     ` Marco Gerards
2008-01-31 10:47                     ` Robert Millan
2008-01-31 11:38                       ` Yoshinori K. Okuji
2008-01-31 12:47                         ` Robert Millan
2008-01-31 13:30                           ` Yoshinori K. Okuji
2008-01-29  8:36   ` Redefining GRUB_MOD_GAP in init.c Marco Gerards
2008-01-29  9:05     ` Robert Millan
2008-01-29  9:21       ` Marco Gerards
2008-01-29  9:27         ` CVS (Re: Redefining GRUB_MOD_GAP in init.c) Robert Millan
2008-01-29 11:15           ` Marco Gerards [this message]
2008-01-29 11:42             ` Yoshinori K. Okuji
2008-01-29 11:25           ` Marco Gerards
2008-01-30 21:35             ` Pavel Roskin

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=87tzkwanmq.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.