From: Rob Browning <rlb@defaultvalue.org>
Cc: mvo@zagadka.ping.de, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: Items blocking release 1.6.1 (2002-04-21)
Date: Mon, 22 Apr 2002 16:12:23 -0500 [thread overview]
Message-ID: <87adrvigjs.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16zkn4-00009O-00@giblet> (Thien-Thi Nguyen's message of "Mon, 22 Apr 2002 13:52:02 -0700")
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> personally, i was foolish to think i could help guile improve w/o
> seeing the folly that it is the guile maintainers who need to
> improve (which is outside my control).
Of course you can help guile improve -- your past history and good
work is proof of that.
I can't speak for everyone else, but I'd really like to try to work
*with* the other maintainers to resolve our outstanding issues. If I
wasn't interested in that I wouldn't be taking the time to do the
things I've been doing, including trying to work out a release process
everyone can agree on that will hopefully help avoid the disagreements
we recently had on the subject.
In this particular case, instead of the response you posted, I'd like
to hear what your specific complaints are wrt bound?, and to hear what
fix you have in mind, if any. For example, you mention using
out-of-band communications, but can this be done in a way that doesn't
force everyone to change their code anyway? If not, then how is it
any different than just removing bound?
Note that these aren't rhetorical questions. I'm not all that
familiar with the issue since it wasn't my bug, and so I'd like to
understand all the considerations.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-22 21:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 20:05 Items blocking release 1.6.1 (2002-04-21) Thien-Thi Nguyen
2002-04-22 20:15 ` Rob Browning
2002-04-22 20:52 ` Thien-Thi Nguyen
2002-04-22 21:12 ` Rob Browning [this message]
2002-04-22 21:25 ` Rob Browning
2002-04-22 21:30 ` Rob Browning
2002-04-22 21:51 ` Thien-Thi Nguyen
2002-04-22 23:03 ` Rob Browning
2002-04-22 20:29 ` Bill Gribble
2002-04-22 21:20 ` Thien-Thi Nguyen
2002-04-23 18:16 ` Marius Vollmer
2002-04-25 9:09 ` tomas
2002-04-25 10:02 ` rm
2002-04-28 16:00 ` Marius Vollmer
2002-04-28 20:27 ` Thien-Thi Nguyen
2002-05-07 18:43 ` Marius Vollmer
2002-04-28 15:58 ` Marius Vollmer
2002-04-28 20:38 ` spu
-- strict thread matches above, loose matches on Subject: below --
2002-04-21 16:22 Rob Browning
2002-04-22 8:35 ` Thien-Thi Nguyen
2002-04-22 13:02 ` Rob Browning
2002-04-22 18:04 ` Marius Vollmer
2002-04-22 18:26 ` Rob Browning
2002-04-22 18:44 ` Marius Vollmer
2002-04-22 18:56 ` Rob Browning
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=87adrvigjs.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mvo@zagadka.ping.de \
/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).