From: Bengt Kleberg <bengt@softwell.se>
To: haahr@jivetech.com, tjg@star.le.ac.uk
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc futures
Date: Fri, 14 Jan 2000 07:16:34 -0500 [thread overview]
Message-ID: <200001141215.NAA01047@trillian.softwell.se> (raw)
> From: Paul Haahr <haahr@jivetech.com>
> Posix mandates path searching for ``.'' in sh.
> But Byron's rc never has, and I don't think it should.
Agree.
next reply other threads:[~2000-01-14 20:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 12:16 Bengt Kleberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-14 12:20 Bengt Kleberg
2000-01-12 21:34 Chet Ramey
2000-01-01 2:55 ` Paul Haahr
2000-01-12 14:22 Bengt Kleberg
2000-01-03 15:46 Bengt Kleberg
1999-12-16 16:40 Chet Ramey
1999-12-16 12:43 Smarasderagd
1999-12-19 11:06 ` Steve Kilbane
1999-12-22 0:00 ` Christopher Vance
1999-12-15 16:32 Russ Cox
1999-12-14 9:44 Byron Rakitzis
1999-12-13 12:55 Elliott Hughes
1999-12-10 16:55 Tim Goodwin
1999-12-13 18:54 ` Paul Haahr
2000-01-04 16:43 ` Tim Goodwin
1999-12-31 23:26 ` Paul Haahr
1999-12-15 0:17 ` Chris Siebenmann
2000-01-07 3:45 ` Decklin Foster
2000-01-01 4:20 ` Paul Haahr
2000-01-15 8:58 ` Steve Kilbane
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=200001141215.NAA01047@trillian.softwell.se \
--to=bengt@softwell.se \
--cc=haahr@jivetech.com \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=tjg@star.le.ac.uk \
/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).