unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: guile-aclocal.sh looks broken.
Date: Tue, 23 Apr 2002 17:50:05 -0700	[thread overview]
Message-ID: <E170Ayz-00071B-00@giblet> (raw)
In-Reply-To: <87lmbqnhvt.fsf@zagadka.ping.de> (message from Marius Vollmer on 14 Apr 2002 22:29:42 +0200)

   From: Marius Vollmer <mvo@zagadka.ping.de>
   Date: 14 Apr 2002 22:29:42 +0200

   I propose to fix this situation [...]   OK?

cool.

i notice autoconf 2.53 now has abs_builddir and friends, so we can
replace our ad-hoc implementations of this functionality, too.

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-04-24  0:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14 20:29 guile-aclocal.sh looks broken Marius Vollmer
2002-04-14 20:35 ` Marius Vollmer
2002-04-24  0:50 ` Thien-Thi Nguyen [this message]
2002-04-26 17:57   ` Marius Vollmer
2002-04-26 19:09     ` Thien-Thi Nguyen
2002-04-27  0:49       ` 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=E170Ayz-00071B-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-devel@gnu.org \
    --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).