From: Herbert Xu <herbert@gondor.apana.org.au>
To: Jilles Tjoelker <jilles@stack.nl>
Cc: aleksandar.ristovski@gmail.com, dash@vger.kernel.org
Subject: Re: shell: dash - large file support
Date: Tue, 28 Jul 2015 10:25:39 +0800 [thread overview]
Message-ID: <20150728022539.GA23798@gondor.apana.org.au> (raw)
In-Reply-To: <20150726192141.GC4346@stack.nl>
Jilles Tjoelker <jilles@stack.nl> wrote:
>
> However, using a non-largefile stat() or lstat() is always wrong, since
> the inode number may not fit in a non-largefile ino_t. This happens in
> various cases: test -ef/-nt/-ot, finding a dot script (. special
> builtin) and some related to the current directory.
>
> On another note, test -nt/-ot should really compare the nanoseconds
> parts as well.
Please send patches for these issues.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2015-07-28 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 18:50 shell: dash - large file support Aleksandar Ristovski
2015-07-26 19:21 ` Jilles Tjoelker
2015-07-28 2:25 ` Herbert Xu [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=20150728022539.GA23798@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=aleksandar.ristovski@gmail.com \
--cc=dash@vger.kernel.org \
--cc=jilles@stack.nl \
/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).