unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: The Big Switch to Git
Date: Mon, 24 Mar 2008 22:56:53 +0000	[thread overview]
Message-ID: <87iqzbloi2.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87abl1uved.fsf@gnu.org> (Ludovic Courtès's message of "Fri, 14 Mar 2008 17:23:38 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Personally, I'm thinking about only importing `guile-core' for now (like
> what Han-Wen did at http://repo.or.cz/w/guile.git some time ago).  If we
> eventually feel the need to import the other modules, we can do it and
> have the Savannah folks let us store them in sub-directories.

After reviewing what others have said on this, I'm inclined to agree
with this lazy-import approach.

> We can't easily setup a `git-cvspserver' on Savannah I'm afraid, nor a
> bidirectional gateway, and I think the complexity of doing it would
> exceed the benefit, especially now that Git has become widespread.
> Thus, I think we should just leave the CVS repository as is.  Of course,
> we don't want to delete it, since it contains other modules, for
> instance.  What do you think?

Agreed.  Except that I think that we should "cvs remove" everything
that has been transferred to Git (once it is clear that the transfer
was successful).  (Because there should not be two possible sources
for the guile-core files, that can only confuse people.)

> Once we've agreed on the details, one of the Savannah admins of the
> project (i.e., Neil) will have to tick the "Git repository" option in
> the "Select Features" menu item of the web interface, after which I can
> just push the repository online.

I think I can go ahead with this at any time, can't I?  In other
words: ticking this option won't automatically do anything bad to the
existing CVS infrastructure, will it?

>  We'll also have to update all
> references to the CVS repository.

Agreed.

Regards,
      Neil





  parent reply	other threads:[~2008-03-24 22:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 16:23 The Big Switch to Git Ludovic Courtès
2008-03-14 18:38 ` Greg Troxel
2008-03-15 21:30   ` Ludovic Courtès
2008-03-16 20:57     ` Thien-Thi Nguyen
2008-03-24 23:16       ` Neil Jerram
2008-03-27 14:07         ` Thien-Thi Nguyen
2008-03-27 14:28           ` Han-Wen Nienhuys
2008-03-27 14:45             ` Thien-Thi Nguyen
2008-03-28  4:33               ` Han-Wen Nienhuys
2008-03-28  7:39                 ` Thien-Thi Nguyen
2008-03-28 16:11                   ` Han-Wen Nienhuys
2008-03-28  8:10                 ` Ludovic Courtès
2008-03-28 16:14                   ` Han-Wen Nienhuys
2008-03-15 16:22 ` Thien-Thi Nguyen
2008-03-22  0:41 ` Han-Wen Nienhuys
2008-03-26 22:36   ` Ludovic Courtès
2008-03-24 22:56 ` Neil Jerram [this message]
2008-03-26 10:06   ` Ludovic Courtès
2008-03-26 18:47     ` Neil Jerram
2008-03-26 22:31       ` Ludovic Courtès
2008-03-27 20:22         ` Ludovic Courtès
2008-03-27 22:16           ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iqzbloi2.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).