From: Neil Jerram <neil@ossau.uklinux.net>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-devel@gnu.org
Subject: Re: The Big Switch to Git
Date: Mon, 24 Mar 2008 23:16:23 +0000 [thread overview]
Message-ID: <87bq53lnlk.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <878x0i2xr7.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Sun, 16 Mar 2008 21:57:00 +0100")
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> It would be nice to have workbook and guile-scripts as peers of
> guile-core, since that forms the minimal set to reproduce "cvs
> checkout hack" of yore. (Basically, the cvs-module "hack"
> included only those three cvs-modules.)
I'm not aware that this "hack" collection has been doing anything for
us recently. At least, it's true that guile-core does not currently
depend on workbook, as it did once.
I'm sure there is stuff in workbook and guile-scripts that is still
useful, but I prefer to import it lazily (and as and when it becomes a
priority). That will also allow us to consider where each imported
item should go within the Git repository.
> Unrelated, i would request that guile-www be imported as well.
> This way, presuming there is interest, we can eventually merge in
> work on Guile-WWW that has been happening ttn-locally[0] for many
> years now.
Wouldn't it make sense for guile-www to be a separate Savannah
project?
In case this sounds like I'm singling out guile-www, I've actually
always had a problem understanding the structure and existence of the
Guile CVS modules other than guile-core - and I think the fact that
many of them are obsolete and/or bitrotted is a clue that this is a
problem in practice.
Regards,
Neil
next prev parent reply other threads:[~2008-03-24 23:16 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 [this message]
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=87bq53lnlk.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ttn@gnuvola.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).