unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS]
Date: Wed, 10 Mar 2004 17:34:01 -0500	[thread overview]
Message-ID: <200403101734.20971.clinton@unknownlamer.org> (raw)
In-Reply-To: <87brn9gajl.fsf@ivanova.rotty.yi.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 06 March 2004 12:17, Andreas Rottmann wrote:
> First, I'm happy to announce the availibility of an Arch "mirror" of
> the Guile CVS. It's located at:
>
> http://people.debian.org/~rotty/arch/rotty@debian.org/guile-2004/
>
> In the category guile-core, there is a cvs-trunk branch, which will
> follow CVS HEAD. I might one day start auto-building Debian packages
> for experimental from that (and maybe other branches).
>       patch-2
>          Applied extended -e patch by Clinton Ebadi
>
>       patch-3
>          Applied getopt-long patch by Clinton Ebadi

You may want to undo the extended -e patch; I had forgotten that Guile CVS now 
reads the argument to -e and the (@ (module) procedure) syntax provides an 
easy enough way to do things. Maybe ttn's extended syntax could be supported 
with another option (-m?) or somehow supported by -e for compatibility with 
his 1.4.1.x tree (I don't really see how that would work, since (foo bar) 
could be a procedure call that returns the entry procedure).

> You might consider branching off that and I'll star-merge your changes
> back in, which lowers effort for both off us (just make sure you
> commit clean changesets, as you've done now).

Never a better time than the present to learn how to use arch.

- -- 
http://unknownlamer.org
AIM:unknownlamer IRC:unknown_lamer@freenode#hprog
I use Free Software because I value freedom over features.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAT5fqdgGh8PQDV0sRAoC5AKDJrLOp5Z+oyS1Ofk7NeFvlTz7oLwCfY7pi
D9MSbKdHrCbq6OLVxDj1fcI=
=vwHk
-----END PGP SIGNATURE-----


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-03-10 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04  1:37 Patches from ttn's tree to Guile CVS Clinton Ebadi
2004-03-06 15:57 ` Neil Jerram
2004-03-10 23:46   ` Marius Vollmer
2004-03-14 10:44     ` Andreas Rottmann
2004-03-21  2:11       ` Marius Vollmer
2004-03-06 17:17 ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Andreas Rottmann
2004-03-10 22:34   ` Clinton Ebadi [this message]
2004-03-12  9:31     ` guile-core in Arch archive Andreas Rottmann
2004-03-10 23:32   ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Tom Lord
2004-03-07 11:04 ` Patches from ttn's tree to Guile CVS Marius Vollmer
2004-03-09 20:35 ` Marius Vollmer
2004-03-09 20:36 ` Marius Vollmer
2004-03-09 20:42 ` Marius Vollmer

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=200403101734.20971.clinton@unknownlamer.org \
    --to=clinton@unknownlamer.org \
    --cc=guile-devel@gnu.org \
    --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).