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 14:16:34 -0700 [thread overview]
Message-ID: <E1707eM-0004IW-00@giblet> (raw)
In-Reply-To: <87vgazuun3.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Wed, 10 Apr 2002 16:10:56 -0500)
From: Rob Browning <rlb@defaultvalue.org>
Date: Wed, 10 Apr 2002 16:10:56 -0500
I've been trying to make sure to migrate all my 1.6 patches to HEAD,
but there are still some outstanding. Of course some of the lag is
because I'm not sure we'll want to handle things the same in 1.8.
hmmm, this is very different way of looking at things from what i would
expect... i'm operating on the assumption that we want to look at
things from long-term perspective first and foremost, and interpolate
current decisions/activities from that. that is, figure out LATER and
then figure out NOW as it relates to LATER, rather than the reverse.
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.
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 21:16 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 [this message]
2002-04-23 22:42 ` Rob Browning
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=E1707eM-0004IW-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).