From: Linus Torvalds <torvalds@osdl.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, git@vger.kernel.org
Subject: Re: full kernel history, in patchset format
Date: Sat, 16 Apr 2005 12:15:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504161208410.7211@ppc970.osdl.org> (raw)
In-Reply-To: <1113681021.28612.29.camel@tglx.tec.linutronix.de>
On Sat, 16 Apr 2005, Thomas Gleixner wrote:
>
> For the export stuff its terrible slow. :(
I don't really see your point.
If you already know what the tree is like you say, you don't care about
the tree object. And if you don't know what the tree is, what _are_ you
doing?
In other words, show us what you're complaining about. If you're looking
into the trees yourself, then the binary representation of the sha1 is
already what you want. That _is_ the hash. So why do you want it in ASCII?
And if you're not looking into the tree directly, but using "cat-file
tree" and you were hoping to see ASCII data, then that's certainly not
going to be any faster than just doing "ls-tree" instead.
In other words, I don't see your point. Either you want ascii output for
scripting, or you don't. First you claimed that you did, and that you
would want the tree object to change in order to do so. Now you claim that
you can't use "ls-tree" because it's too slow.
That just isn't making any sense. You're mixing two totally different
levels, and complaining about performance when scripting things. Yet
you're talking about a 20-byte data structure that is trivial to convert
to any format you want.
What kind of _strange_ scripting architecture is so fast that there's a
difference between "cat-file" and "ls-tree" and can handle 17,000 files in
60,000 revisions, yet so slow that you can't trivially convert 20 bytes of
data?
Linus
next prev parent reply other threads:[~2005-04-16 19:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 13:15 full kernel history, in patchset format Ingo Molnar
2005-04-16 13:35 ` Ingo Molnar
2005-04-16 14:55 ` David Mansfield
2005-04-16 19:18 ` Ingo Molnar
2005-04-16 15:08 ` Francois Romieu
2005-04-16 17:04 ` Linus Torvalds
2005-04-16 17:43 ` Petr Baudis
2005-04-16 15:44 ` Christopher Li
2005-04-16 18:31 ` Junio C Hamano
2005-04-16 18:35 ` Mike Taht
2005-04-16 19:19 ` Junio C Hamano
2005-04-16 16:26 ` Christopher Li
2005-04-16 19:44 ` Junio C Hamano
2005-04-16 19:42 ` Mike Taht
2005-04-16 20:19 ` Daniel Barkalow
2005-04-16 18:46 ` Junio C Hamano
2005-04-16 19:13 ` Jan-Benedict Glaw
2005-04-16 19:23 ` Thomas Gleixner
2005-04-16 18:32 ` Petr Baudis
2005-04-16 18:36 ` Petr Baudis
2005-04-16 19:41 ` Thomas Gleixner
2005-04-16 18:44 ` Linus Torvalds
2005-04-16 19:50 ` Thomas Gleixner
2005-04-16 18:57 ` Petr Baudis
2005-04-16 19:27 ` Junio C Hamano
2005-04-16 19:15 ` Linus Torvalds [this message]
2005-04-16 20:35 ` Thomas Gleixner
2005-04-16 23:08 ` David Lang
2005-04-16 19:41 ` Ingo Molnar
2005-04-17 23:31 ` David Woodhouse
2005-04-17 23:39 ` Petr Baudis
2005-04-18 0:06 ` David Woodhouse
2005-04-18 0:35 ` Petr Baudis
2005-04-18 0:45 ` David Woodhouse
2005-04-18 0:50 ` Petr Baudis
2005-04-18 0:51 ` David Woodhouse
2005-04-18 0:59 ` Petr Baudis
2005-04-18 1:16 ` Linus Torvalds
2005-04-18 1:36 ` David Woodhouse
2005-04-18 10:07 ` Catalin Marinas
2005-04-18 22:41 ` David Mansfield
2005-04-19 8:33 ` Catalin Marinas
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0504161208410.7211@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).