From: Daniel Skarda <0rfelyus@ucw.cz>
Subject: Re: srfi-26
Date: Sat, 24 Jan 2004 11:22:37 +0100 [thread overview]
Message-ID: <m0hdyl7ij6.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <8765f31okc.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 23 Jan 2004 10:44:19 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> It'll be needing a copyright notice. What years does it date from?
I wrote my cute cut implementation few days before I sent it to guile-devel.
September - October 2002, I guess.
0.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-24 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 2:17 srfi-26 Alex Shinn
2004-01-15 9:36 ` srfi-26 Daniel Skarda
2004-01-21 0:44 ` srfi-26 Marius Vollmer
2004-01-23 0:44 ` srfi-26 Kevin Ryde
2004-01-24 10:22 ` Daniel Skarda [this message]
2004-02-28 20:15 ` srfi-26 Kevin Ryde
2004-02-29 10:04 ` srfi-26 Daniel Skarda
2004-03-01 21:10 ` srfi-26 Kevin Ryde
2004-01-15 22:08 ` srfi-26 Kevin Ryde
2004-01-16 3:28 ` srfi-26 Alex Shinn
2004-01-16 4:13 ` srfi-26 Paul Jarc
2004-01-16 18:53 ` srfi-26 Greg Troxel
2004-01-19 8:22 ` srfi-26 Alex Shinn
2004-01-19 16:43 ` srfi-26 Stephen Compall
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=m0hdyl7ij6.fsf@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
/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).