From: "Marco Costalba" <mcostalba@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Paul Mackerras" <paulus@samba.org>,
"Brett Schwarz" <brett_schwarz@yahoo.com>,
"Karl Hasselstr?m" <kha@treskal.com>,
"Junio C Hamano" <junkio@cox.net>,
"Carl Worth" <cworth@cworth.org>,
"Michael Niedermayer" <michaelni@gmx.at>,
"Git Mailing List" <git@vger.kernel.org>
Subject: --stdin option for 'git log' [was FFmpeg considering GIT]
Date: Fri, 11 May 2007 13:13:45 +0200 [thread overview]
Message-ID: <e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@mail.gmail.com> (raw)
On 5/8/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Well, we actually do have that. "git log" (or "git-rev-list") really does
> all the heavy lifting. The reason you can do things like "gitk --merge" is
> not because gitk itself has _any_ idea about anything, but because it just
> passes the arguments down to git-rev-list (and hopefully soon git log),
> which really does all the complex stuff.
>
To replace 'git rev-list' with 'git log' an important missing feature,
at least for me, is the support for '--stdin' option of 'git-rev-list'
that currently seems missing in 'git log'
I found this limit while trying to use 'git log' instead of 'git
rev-list'. The problem is that command line arguments could be very
long in some cases, typically when passing a list of sha's values (as
example all the branches sha). This happens of course when 'git log'
is run by script/applications not directly by the user.
Under Linux, command line arguments size limits are _normaly_ enough
(you could have problems for repository with hundreds of
tags/branches), but under *others* OS we are not so lucky.
So with '--stdin' you have an elegant solution to support any kind of
repository under any OS ignoring the platform limit on command line
length.
Marco
reply other threads:[~2007-05-11 11:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=brett_schwarz@yahoo.com \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kha@treskal.com \
--cc=michaelni@gmx.at \
--cc=paulus@samba.org \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).