From: Clinton Ebadi <clinton@unknownlamer.org>
Subject: Patches from ttn's tree to Guile CVS
Date: Wed, 3 Mar 2004 20:37:53 -0500 [thread overview]
Message-ID: <200403032038.07053.clinton@unknownlamer.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://unknownlamer.org/files/code/scheme/patches/guile-cvs will now contain
all of the patches against Guile CVS HEAD which add features from ttn's tree.
I am making each change a separate patch (cleaner that way).
Is there any chance of these ever being merged?
- --
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)
iD8DBQFARoh9dgGh8PQDV0sRAlqcAJ96eCLftYXoWlVWcRFVh5vnxTFaZACghhR/
0lZcFQbeAphlB4Eg95U/t+k=
=WTV8
-----END PGP SIGNATURE-----
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-03-04 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 1:37 Clinton Ebadi [this message]
2004-03-06 15:57 ` Patches from ttn's tree to Guile CVS 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
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-06 20:01 ` Patches from ttn's tree to Guile CVS Thamer Al-Harbash
2004-03-07 11:04 ` 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=200403032038.07053.clinton@unknownlamer.org \
--to=clinton@unknownlamer.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).