From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "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: Re: gitk and git-gui, was Re: FFmpeg considering GIT
Date: Tue, 8 May 2007 08:33:09 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705080830380.3974@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705081311550.4167@racer.site>
On Tue, 8 May 2007, Johannes Schindelin wrote:
>
> It might be a much better idea to write something a la git-fetch--tool,
> which is a helper in C (thus very fast and memory efficient), outputting
> easily parseable data.
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.
But gitk still ends up having a big memory footpring, simply because if
you get the data for a few hundred thousand commits (with commit messages
etc), and have to keep track of the relationships between them, you are
going to easily use hundreds of megs of memory.
Linus
prev parent reply other threads:[~2007-05-08 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 3:39 FFmpeg considering GIT Brett Schwarz
2007-05-08 4:06 ` Paul Mackerras
2007-05-08 4:19 ` Shawn O. Pearce
2007-05-08 11:16 ` gitk and git-gui, was " Johannes Schindelin
2007-05-08 15:33 ` Linus Torvalds [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=alpine.LFD.0.98.0705080830380.3974@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--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 \
/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