From: Carlo Strozzi <carlos@linux.it>
To: rc@hawkwind.utcs.utoronto.ca
Subject: Re: path oddity
Date: Wed, 3 May 2000 13:12:10 -0400 [thread overview]
Message-ID: <20000503191210.A19441@tango.texne.com> (raw)
Regarding my previous message, I forgot to add that if I set a shorter
path, like (/bin /usr/bin /usr/local/bin), then everything works fine
even without adding the bogus path at the end.
bye -carlo
--
I can read MIME or uuencoded e-mail attachments in PDF, Postscript, HTML,
RTF or text formats. Please do not send Word or Excel files.
next reply other threads:[~2000-05-04 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 17:12 Carlo Strozzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-03 17:07 Carlo Strozzi
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=20000503191210.A19441@tango.texne.com \
--to=carlos@linux.it \
--cc=carlos@texne.com \
--cc=rc@hawkwind.utcs.utoronto.ca \
/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).