From: Rob Browning <rlb@defaultvalue.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 17:42:58 -0500 [thread overview]
Message-ID: <87wuuy82a5.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E1707eM-0004IW-00@giblet> (Thien-Thi Nguyen's message of "Tue, 23 Apr 2002 14:16:34 -0700")
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> in practice, this means changing HEAD branch to conform to LATER first,
> and branch_release-1-6 to conform to NOW. to me this seems like less
> work.
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.
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.
--
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
_______________________________________________
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:42 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 [this message]
2002-04-23 22:50 ` Thien-Thi Nguyen
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=87wuuy82a5.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=bug-guile@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).