From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Maciek Godek" <pstrychuj@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: What happened to the infix module?
Date: Sat, 2 Aug 2008 18:10:57 +0100 [thread overview]
Message-ID: <49dd78620808021010o5cc661b9i860eba83095fe514@mail.gmail.com> (raw)
In-Reply-To: <e2ceda030808020709w56467807vff70d972e2c2461f@mail.gmail.com>
2008/8/2 Maciek Godek <pstrychuj@gmail.com>:
>
> Oh, I finally have my chance to ask:
> why was the guile 1.4 fork created?
There was an argument in about May 2005 between Thien-Thi and the
maintainer at the time (Marius Vollmer). It began technically, but
became a bit unpleasant, and Marius felt that he had to revoke
Thien-Thi's ability to commit to the Guile CVS repository.
And so on, from there...
Neil
prev parent reply other threads:[~2008-08-02 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 12:10 What happened to the infix module? Maciek Godek
2008-08-02 12:45 ` Thien-Thi Nguyen
2008-08-02 14:09 ` Maciek Godek
2008-08-02 17:10 ` Neil Jerram [this message]
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=49dd78620808021010o5cc661b9i860eba83095fe514@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-user@gnu.org \
--cc=pstrychuj@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).