From: John (_You_ hide, they seek.) Mackin <john@civil.su.oz.au>
To: Byron Rakitzis <byron@netapp.com>
Cc: Boyd Roberts <boyd@prl.dec.com>,
The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: compact - a history-file compaction command
Date: Sun, 4 Oct 1992 01:57:30 -0400 [thread overview]
Message-ID: <199210041557.18168.rc.babuf@civil.su.oz.au> (raw)
In-Reply-To: <9210040550.AA16988@netapp.netapp.com>
tac | onlyfirst | tac
Sorry, Byron, but I don't buy this (as you already know). Here's why:
sure, I already had "revfile". Sure, "revfile"/"tac" is independently
useful (_very_ useful). It's the _middle_ of the pipeline I'm against.
Are you going to claim that onlyfirst is any more generally useful
than compact? If so, please give examples, because I don't think it
is. From a slightly abstract point of view, they are nearly the same
program (compact could have been called "onlylast").
OK,
John.
next prev parent reply other threads:[~1992-10-04 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-10-04 5:50 Byron Rakitzis
1992-10-04 5:57 ` John Mackin [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-10-04 6:20 Byron Rakitzis
1992-10-03 23:17 John Mackin
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=199210041557.18168.rc.babuf@civil.su.oz.au \
--to=john@civil.su.oz.au \
--cc=boyd@prl.dec.com \
--cc=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.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).