unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: The Big Switch to Git
Date: Sat, 15 Mar 2008 22:30:51 +0100	[thread overview]
Message-ID: <87wso3u12s.fsf@gnu.org> (raw)
In-Reply-To: rmi63vpnoc7.fsf@fnord.ir.bbn.com

Hi,

Greg Troxel <gdt@ir.bbn.com> writes:

> I would be tempted to transfer the other modules; the plan you stated
> leaves some things in cvs and some not, and you want to disable writes
> to cvs after the cutover.  It would be cleaner to have all in git and
> cvs just a historical reference.

Just to clarify: there are 18 modules, most of which are interesting,
but also somewhat bitrotten.  Here's the list:

  guile-comp        guile-modules   guile-statprof  guile-www
  guile-core        guile-oops      guile-tcltk     qscheme
  guile-doc         guile-rgx-ctax  guile-template  workbook
  guile-gtkthreads  guile-scripts   guile-tk
  guile-lightning   guile-scsh      guile-vm

I did some work on Guile-VM (in another repository, but it could be
merged), so this one is slightly less outdated.  `guile-statprof' is now
known as `(statprof)' in Guile-Lib.  `guile-oops' has been part of Guile
for several years.  `workbook' contains valuable but somewhat outdated
(?) documentation.  And the others, well...

That's why the "lazy import" method I was suggesting seemed worthwhile
(and also much less resource-consuming ;-)).

That said, we could agree on a subset of these modules that we'd import
from the beginning and let a few others rest in peace?

Thanks,
Ludovic.





  reply	other threads:[~2008-03-15 21:30 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 [this message]
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
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=87wso3u12s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-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 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).