From: "peter a. cejchan" <pac@next.gli.cas.cz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] longnamelist
Date: Mon, 8 Apr 2002 13:01:08 +0000 [thread overview]
Message-ID: <71652467.0204050105.c7298fd@posting.google.com> (raw)
In-Reply-To: <200204050135.g351ZuUL031489@theraft.strakt.com>
boyd@strakt.com (Boyd Roberts) wrote in message news:<200204050135.g351ZuUL031489@theraft.strakt.com>...
> during compilation, a file called 'longnamelist' has been generated.
>
> Sounds more like tar(1) to me when you exceed the max length
> of a directory entry component (as distinct from the length
> of the whole pathname).
yes, you're right: the name is just relative to the extract dir. tx,
++pac.
prev parent reply other threads:[~2002-04-08 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 17:16 pac
2002-04-05 1:35 ` Boyd Roberts
2002-04-08 13:01 ` peter a. cejchan [this message]
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=71652467.0204050105.c7298fd@posting.google.com \
--to=pac@next.gli.cas.cz \
--cc=9fans@cse.psu.edu \
/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).