All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: rename grub to grub-legacy ?
Date: Thu, 09 Oct 2008 11:36:51 -0400	[thread overview]
Message-ID: <1223566611.28088.30.camel@dv> (raw)
In-Reply-To: <1223546020.4143.1.camel@fz.local>

On Thu, 2008-10-09 at 11:53 +0200, Felix Zielcke wrote:
> Am Dienstag, den 07.10.2008, 21:24 +0200 schrieb Yoshinori K. Okuji:
> > 
> > I have no objection. Sorry for a slow response.
> 
> So if I understand it right then
> `svn mv svn+ssh://svn.sv.gnu.org/grub/trunk/grub svn+ssh://svn.sv.gnu.org/grub/trunk/grub-legacy'
> should do it, inclusive saving the history?
> I just better ask before trying it out :)

Preserving history is not perfect.  I believe it's impossible to refer
to the old revisions by the new names in diff, so one would need to use
old paths for the pre-move revisions.  Anyway, "svn mv" is the
Subversion way of doing things.  If we are certain that we want to move
the repository, it's better to do it early.  It's also better to do it
when there are no unmerged branches.

I believe Okuji wanted to use a different naming scheme, that would put
"grub2" or "grub-legacy" above trunk.  You may want to check it to avoid
moving things twice.

All the above notwithstanding, I'm still skeptical about the whole
moving idea based on my experience with other projects.  Repositories
are for developers and should be used in the way that minimizes troubles
for developers rather than reduces the entry barrier for newbies.

If GRUB2 is moved in any way, I'm not sure I'll be able to keep the git
mirror at repo.or.cz up to date.  It doesn't seem that git-svn can deal
with it.  I'm going to try to keep is running, but I cannot promise it.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-10-09 15:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 14:48 rename grub to grub-legacy ? Robert Millan
2008-08-01 15:09 ` Marco Gerards
2008-08-01 15:39   ` Robert Millan
2008-08-03 20:04     ` Robert Millan
2008-08-03 23:19       ` Gregg Levine
2008-08-04  5:06       ` Pavel Roskin
2008-10-07 17:36     ` Felix Zielcke
2008-10-07 19:24       ` Yoshinori K. Okuji
2008-10-09  9:53         ` Felix Zielcke
2008-10-09 15:36           ` Pavel Roskin [this message]
2008-10-09 15:58             ` Felix Zielcke
2008-10-10 22:06               ` Pavel Roskin
2008-10-12  1:53               ` Gregg C Levine
2008-11-29 17:02             ` Robert Millan
2008-08-01 15:15 ` Gregg C Levine

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=1223566611.28088.30.camel@dv \
    --to=proski@gnu.org \
    --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.