From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: mvo@zagadka.ping.de, bug-guile@gnu.org
Subject: Re: guile-snarf writes to $srcdir, which is not kosher
Date: Tue, 23 Apr 2002 15:50:34 -0700 [thread overview]
Message-ID: <E17097K-0006se-00@giblet> (raw)
In-Reply-To: <87wuuy82a5.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Tue, 23 Apr 2002 17:42:58 -0500)
From: Rob Browning <rlb@defaultvalue.org>
Date: Tue, 23 Apr 2002 17:42:58 -0500
Depends on the problem. For example, the recent library name changes
relating to libltdl/dlopen issues may or may not belong in HEAD, but
they're critical for 1.6.
the recent changes may or may not belong in HEAD but the questions i'm
asking are: (1) what *does* belong in HEAD?
(2) how does the 1.6 library handling relate to (1)?
Since it's very likely we'll choose a different long-term solution
for this problem, and we won't know until we have the discussion, in
my judgement there was little point in trying to integrate the
changes into HEAD right now.
of course these things follow. i'm not questioning the consequence of
the approach, but the wisdom of using that approach in the first place,
which seems backwards and make-work-ful to me.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-04-23 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 22:55 guile-snarf writes to $srcdir, which is not kosher Marius Vollmer
2002-04-08 2:35 ` Thien-Thi Nguyen
2002-04-08 16:45 ` Marius Vollmer
2002-04-08 19:34 ` Thien-Thi Nguyen
2002-04-09 17:03 ` Marius Vollmer
2002-04-22 7:58 ` Thien-Thi Nguyen
2002-04-10 21:10 ` Rob Browning
2002-04-23 21:16 ` Thien-Thi Nguyen
2002-04-23 22:42 ` Rob Browning
2002-04-23 22:50 ` Thien-Thi Nguyen [this message]
2002-04-23 23:09 ` Rob Browning
2002-04-23 23:51 ` 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=E17097K-0006se-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=mvo@zagadka.ping.de \
--cc=ttn@glug.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).