From: Oleg Verych <olecom@gmail.com>
To: Guido Berhoerster <guido+kernel.org@berhoerster.name>
Cc: dash@vger.kernel.org
Subject: Re: test -nt/-ot behavior
Date: Sun, 21 Feb 2010 15:10:04 +0200 [thread overview]
Message-ID: <8499950a1002210510k49fd54dds74b78f69319eecb0@mail.gmail.com> (raw)
In-Reply-To: <20100221122100.GA9005@wopr.local.invalid>
2010/2/21, Guido Berhoerster <guido+kernel.org@berhoerster.name>:
> So IMHO the consequence for ash should be to either merge the fix from pdksh
> or to drop -nt, -ot, and -ef altogether,
> I would prefer that
> latter since I think silently changing the behavior in an
> incompatible way is bad practice and these features are not
> specified in POSIX anyway.
Me is for the first + `sed` script to add `test -e &&` stuff in
bug-oriented scripts, for bug compatibility.
Breaking stuff is not building useful features.
> --
> Guido Berhoerster
--
sed 'sed && sh + olecom = love' << ''
-o--=O`C
#oo'L O
<___=E M
next prev parent reply other threads:[~2010-02-21 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 12:21 test -nt/-ot behavior Guido Berhoerster
2010-02-21 13:10 ` Oleg Verych [this message]
2010-02-22 6:50 ` Herbert Xu
2010-02-22 10:33 ` Guido Berhoerster
2010-02-23 2:32 ` Herbert Xu
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=8499950a1002210510k49fd54dds74b78f69319eecb0@mail.gmail.com \
--to=olecom@gmail.com \
--cc=dash@vger.kernel.org \
--cc=guido+kernel.org@berhoerster.name \
/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