From: Gaute B Strokkenes <gs234@cam.ac.uk>
Cc: Denys Duchier <Denys.Duchier@ps.uni-sb.de>, ding@gnus.org
Subject: Re: Makefile bug.
Date: 17 May 2001 01:19:15 +0100 [thread overview]
Message-ID: <4ar8xoygho.fsf@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <vafofstbajo.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "16 May 2001 17:03:55 +0200")
On 16 May 2001, Kai.Grossjohann@CS.Uni-Dortmund.DE wrote:
> On 16 May 2001, Gaute B. Strokkenes wrote:
>
>> Personally, I'd rather see that Makefile.in thing fixed. Surely
>> I'm not the only one who's seeing this?
>
> It's not the job of the Makefile to do tilde expansion, that's the
> job of the shell. I don't think it's a good idea to want to do
> tilde expansion in the Makefile -- while expanding `~' does not
> appear to be difficult (just use $HOME), consider `~jrl' which is
> not so easy (the user could be in /etc/passwd, or NIS, or NIS+, or
> NetInfo).
You're confused. This is not what I'm talking about at all; please
re-read my original message.
--
Big Gaute http://www.srcf.ucam.org/~gs234/
.. If I cover this entire WALL with MAZOLA, wdo I have to give my
AGENT ten per cent??
next prev parent reply other threads:[~2001-05-17 0:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 6:46 Gaute B Strokkenes
2001-05-16 9:41 ` Kai Großjohann
2001-05-16 9:51 ` Peter Makholm
2001-05-16 10:09 ` Gaute B Strokkenes
2001-05-16 10:50 ` Kai Großjohann
2001-05-16 12:32 ` Denys Duchier
2001-05-16 13:11 ` Kai Großjohann
2001-05-16 15:18 ` Denys Duchier
2001-05-16 14:20 ` Gaute B Strokkenes
2001-05-16 15:03 ` Kai Großjohann
2001-05-17 0:19 ` Gaute B Strokkenes [this message]
2001-05-17 8:45 ` Kai Großjohann
2001-05-16 12:38 ` Michael.Cook
2001-05-16 14:27 ` Karl Kleinpaste
2001-05-16 15:07 ` Kai Großjohann
2001-05-16 16:34 ` Alexandre Oliva
2001-05-17 0:21 ` Gaute B Strokkenes
2001-05-16 18:55 ` Raja R Harinath
2001-05-17 8:45 ` Kai Großjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ar8xoygho.fsf@kern.srcf.societies.cam.ac.uk \
--to=gs234@cam.ac.uk \
--cc=Denys.Duchier@ps.uni-sb.de \
--cc=ding@gnus.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 NNTP newsgroup(s).