From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Jacobowitz <dan@debian.org>, Petr Baudis <pasky@ucw.cz>,
Greg KH <greg@kroah.com>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes
Date: Thu, 21 Apr 2005 00:22:48 -0400 [thread overview]
Message-ID: <20050421042248.GA16002@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504202056310.2344@ppc970.osdl.org>
On Wed, Apr 20, 2005 at 09:00:44PM -0700, Linus Torvalds wrote:
> > My logic: it's a lot more intuitive to say "cg-log | less" to get
> > paginated output than it is to say "cg-log | cat" to get unpaginated
> > output.
> I disagree.
>
> There is _never_ any valid situation where you do "cg-log" with
> unpaginated output to a tty.
>
> In _any_ real system you'll be getting thousands of lines of output.
> Possibly millions. unpaginated? What the hell are you talking about?
>
> And as I pointed out, if the output is not a tty, then both less and more
> automatically turn into cat, so there's no difference. This change _only_
> triggers for a tty, and I dare you to show a single relevant project where
> it's ok to scroll thousands of lines.
>
> Even git-pasky, which is just a two-week-old project right now outputs
> 4338 lines of output to "git log".
>
> Unpaginated? You must be kidding.
>
> (But if you are _that_ fast a reader, then hey, use "PAGER=cat", and
> you'll find yourself happy).
I used to do 'bk changes | grep \[AGPGART\] -C3 | head' on a regular basis,
just to be able to answer 'hey, did cset x get into tree y?' questions from users.
which is the probably the closest I came to non-paginated usage.
(though, ok 'head' is technically a pager too..)
Dave
next prev parent reply other threads:[~2005-04-21 4:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 20:56 [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Petr Baudis
2005-04-20 21:03 ` Petr Baudis
2005-04-20 21:19 ` Greg KH
2005-04-20 21:51 ` Mike Taht
2005-04-20 21:58 ` Joshua T. Corbin
2005-04-20 21:51 ` Petr Baudis
2005-04-20 21:54 ` Randy.Dunlap
2005-04-20 22:07 ` Steven Cole
2005-04-20 22:09 ` Linus Torvalds
2005-04-20 22:28 ` Petr Baudis
2005-04-20 23:04 ` Greg KH
2005-04-21 0:14 ` Linus Torvalds
2005-04-21 1:12 ` Linus Torvalds
2005-04-21 3:35 ` Daniel Jacobowitz
2005-04-21 2:45 ` Sean
2005-04-21 4:00 ` Linus Torvalds
2005-04-21 4:22 ` Dave Jones [this message]
2005-04-21 5:08 ` Junio C Hamano
2005-04-21 4:28 ` Daniel Jacobowitz
2005-04-21 6:49 ` Petr Baudis
2005-04-21 14:21 ` Edgar Toernig
2005-04-21 16:42 ` Petr Baudis
2005-04-24 0:09 ` Paul Jackson
2005-04-21 5:14 ` Randy.Dunlap
2005-04-21 4:27 ` Sean
2005-04-21 5:29 ` Greg KH
2005-04-24 0:12 ` Paul Jackson
2005-04-21 2:48 ` Matthias Urlichs
2005-04-21 18:15 ` Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes) David A. Wheeler
2005-04-21 7:49 ` [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Ingo Molnar
2005-04-25 11:27 ` Andrew Morton
2005-04-21 2:53 ` Bryan Donlan
2005-04-21 7:36 ` Petr Baudis
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=20050421042248.GA16002@redhat.com \
--to=davej@redhat.com \
--cc=dan@debian.org \
--cc=git@vger.kernel.org \
--cc=greg@kroah.com \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.