From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-user@gnu.org
Subject: Re: Arch and Guile
Date: Tue, 02 Mar 2004 01:23:40 +0100 [thread overview]
Message-ID: <87brng3xmb.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <E1AxwVC-0008W4-00@surf.glug.org> (Thien-Thi Nguyen's message of "Tue, 02 Mar 2004 00:07:10 +0100")
Thien-Thi Nguyen <ttn@surf.glug.org> writes:
> Such a gateway is very simple to use: You have someone who is the
> "Gatekeeper" between the Arch and CVS world. This person then merges
> stuff form other people's branches into the dedicated "CVS" branch,
> which is synced with CVS in both directions.
>
> well, we already have capable goal keepers keeping the cvs sources pure
> from the corrupting influence of users, so probably there is no need for
> more of the same.
>
Since the Gatekeeper needs CVS write access, he needs to be one of
those "goal keepers" (typo?) anyway.
> [...] a CVS-tracking-but-not-commit gateway as described above.
> Actually, this sounds like a good intermediate plan.
>
> to me it sounds like a very good plan, even if not intermediate. a
> constellation of source trees, one of which can be labeled "official"
> but not requiring any particular additional attention (unless something
> tasty appears there).
>
Yeah. I have hoped my SRFI-35 implementation could be considered
"something tasty" (it's more or less complete now), but so far, there
was no response to this :-(
Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Make free software, not war!
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-02 0:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 3:32 Extended -e syntax Clinton Ebadi
2004-03-01 5:04 ` Andreas Rottmann
2004-03-01 11:10 ` Thien-Thi Nguyen
2004-03-01 14:27 ` Arch and Guile Andreas Rottmann
2004-03-01 19:04 ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14 ` ITLA Andreas Rottmann
2004-03-01 21:55 ` ITLA Tom Lord
2004-03-02 0:11 ` ITLA Andreas Rottmann
2004-03-02 2:50 ` ITLA Tom Lord
2004-03-02 14:04 ` ITLA Andreas Rottmann
2004-03-02 3:26 ` ITLA Miles Bader
2004-03-03 11:22 ` ITLA Neil Jerram
2004-03-03 11:55 ` ITLA Andreas Rottmann
2004-03-04 13:55 ` Archive of library modules for Guile Andreas Rottmann
2004-03-04 20:49 ` Neil Jerram
2004-03-04 23:00 ` Andreas Rottmann
2004-03-07 17:33 ` Thamer Al-Harbash
2004-03-07 18:17 ` Thien-Thi Nguyen
2004-03-01 23:07 ` Arch and Guile Thien-Thi Nguyen
2004-03-02 0:23 ` Andreas Rottmann [this message]
2004-03-03 13:01 ` Thien-Thi Nguyen
2004-03-01 11:21 ` Extended -e syntax Thien-Thi Nguyen
2004-03-01 20:20 ` Christopher Cramer
2004-03-02 4:55 ` Clinton Ebadi
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
2004-03-10 18:59 ` ttn's build system Andreas Rottmann
2004-03-10 22:28 ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22 ` Tom Lord
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=87brng3xmb.fsf@alice.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=guile-user@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).