From: Peter Cordes <peter@cordes.ca>
To: "Pádraig Brady" <P@draigBrady.com>
Cc: Ruediger Meier <sweet_f_a@gmx.de>, util-linux@vger.kernel.org
Subject: Re: tailf, really needed?
Date: Sat, 14 Mar 2015 01:50:14 -0300 [thread overview]
Message-ID: <20150314045014.GO3933@cordes.ca> (raw)
In-Reply-To: <5502CBFF.6090405@draigBrady.com>
On Fri, Mar 13, 2015 at 11:37:35AM +0000, Pádraig Brady wrote:
> On 13/03/15 09:00, Ruediger Meier wrote:
> >
> > Last but not least, is anybody using tailf at all? Google does not find
> > much about people who are using this.
>
> A deprecation warning makes sense to me.
I haven't checked the semantics carefully, but could we just turn
tailf into a wrapper for tail -f, to avoid maintaining code that's
gotten old and crufty? And if there aren't corner cases where someone
might still want the old tailf, until it's finally removed from
util-linux.
something like:
#!/bin/sh
if [ "$(tty <&2)" != "not a tty" ];then
echo "warning: tailf is deprecated, and just a wrapper for tail -f" >&2
fi
exec tail -f "$@"
Or is this just asking for gratuitous breakage and confusion beyond
what any existing users will get when they upgrade to a util-linux
where it's finally dropped after a few years of deprecation?
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC
prev parent reply other threads:[~2015-03-14 4:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:00 tailf, really needed? Ruediger Meier
2015-03-13 9:32 ` Sami Kerola
2015-03-13 11:37 ` Pádraig Brady
2015-03-13 13:02 ` Ruediger Meier
2015-03-13 13:35 ` Pádraig Brady
2015-03-13 14:02 ` Ruediger Meier
2015-03-13 20:22 ` Ángel González
2015-03-14 4:50 ` Peter Cordes [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=20150314045014.GO3933@cordes.ca \
--to=peter@cordes.ca \
--cc=P@draigBrady.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.org \
/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