From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Do you recognize these modules?
Date: Mon, 14 May 2012 10:04:03 +0200 [thread overview]
Message-ID: <8762bz89zg.fsf@gnuvola.org> (raw)
In-Reply-To: CA+U71=N-oJcz=hwpsfDiGAVcYxV4wmPFkQ6QdyQcDEO91nFz6w@mail.gmail.com
() Noah Lavine <noah.b.lavine@gmail.com>
() Wed, 2 May 2012 11:26:22 -0400
Unfortunately, it looks like the changes for these do not have
copyright assigned to the FSF, so we can't use them directly.
Is that correct?
Partially (details below).
Also, I hope this isn't a sensitive topic, but why is there a
semi-friendly fork of Guile 1.4? Are there things that you want
to accomplish that Guile 2.0 can't do? Or maybe you want
complete compatibility with Guile 1.4 - even so, why fork?
It's not sensitive, but it's not a short answer, either...
[maudlin recollections snipped -- i will publish these separately.]
The short answer is that the fork (from 2001 or so) was a reaction
to losing repo write privs. Now that i have regained them, i am
interested in merging back the relevant bits, w/ copyright notice
modified to the proper FSF standards. Details up to you...
I see from another post you have decided to rewrite, due to my
delayed response. Sorry about that. I anticipate my ability to
keep up in the foreseeable future to be likewise limited, so if
you're still interested, please let me know what i must do to get
these bits in-tree and useful to you (and others) as a basis for
further maintenance (kind of a one-shot mass-transfer).
Thanks for taking care of 1.8, btw -- i am sure i'm not alone in
appreciating this work.
next prev parent reply other threads:[~2012-05-14 8:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 22:26 Do you recognize these modules? Noah Lavine
2012-05-01 23:22 ` Thien-Thi Nguyen
2012-05-02 15:26 ` Noah Lavine
2012-05-14 8:04 ` Thien-Thi Nguyen [this message]
2012-05-14 10:52 ` Noah Lavine
2012-05-14 12:59 ` David Kastrup
2012-05-14 13:59 ` Noah Lavine
2012-05-14 14:12 ` David Kastrup
2012-05-14 12:44 ` Ludovic Courtès
2012-05-14 17:00 ` Thien-Thi Nguyen
2012-05-14 17:30 ` Noah Lavine
2012-05-15 20:14 ` Andy Wingo
2012-05-25 8:53 ` Thien-Thi Nguyen
2012-05-25 12:48 ` Andy Wingo
2012-05-25 17:02 ` Thien-Thi Nguyen
2012-07-11 3:02 ` Noah Lavine
2012-07-11 7:21 ` Thien-Thi Nguyen
2012-07-11 10:44 ` Andy Wingo
2012-07-11 15:20 ` Noah Lavine
2012-07-11 17:59 ` Noah Lavine
2012-08-25 22:27 ` Noah Lavine
2012-08-26 20:47 ` Ludovic Courtès
2013-03-23 10:36 ` Thien-Thi Nguyen
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=8762bz89zg.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).