Re: Re: full kernel history, in patchset format
- From
Petr Baudis <pasky@ucw.cz>
- Date
- Apr 16, 2005, 18:57 UTC
- Message-ID
- <20050416185751.GJ19099@pasky.ji.cz>
- In-Reply-To
- <1113681021.28612.29.camel@tglx.tec.linutronix.de>
Dear diary, on Sat, Apr 16, 2005 at 09:50:21PM CEST, I got a letter where Thomas Gleixner <tglx@linutronix.de> told me that...
Show 10 quoted lines
> On Sat, 2005-04-16 at 11:44 -0700, Linus Torvalds wrote:
>
> > That level of abstraction ("we never look directly at the objects") is
> > what allows us to change the object structure later. For example, we
> > already changed the "commit" date thing once, and the tree object has
> > obviously evolved a bit, and if we ever change the hash, the objects will
> > change too, but if you always just script them using nice helper tools,
> > you won't ever need to _care_. And that's how it should be.
>
> For the export stuff its terrible slow. :(It seems to me that you must be doing something wrong then. I can't see anything which would not make ls-tree blindingly fast (except for when being recursive, see below).
BTW, what do you need ls-tree output for, when doing export _to_ git?
P.S.: It seems that Linus applied a patch to ls-tree which will make it read_sha1_file() on each item when ls-tree is recursive. Junio, why did you do it? Is there any possible case when the item would not be marked as directory but it would be a tree object? I could imagine it bogging down ls-tree on big tree a lot.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor