From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] Use struct tree in diff-tree
Date: Tue, 31 Jan 2006 14:07:30 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601311337500.7301@g5.osdl.org> (raw)
In-Reply-To: <7virs0uma8.fsf@assigned-by-dhcp.cox.net>
On Tue, 31 Jan 2006, Junio C Hamano wrote:
>
> The one to git-tar-tree I've already applied, mostly because I
> was not careful enough and especially I did not care enough
> about performance of that program. On my slow machine the tip
> of kernel before you came back takes 9.2 seconds wallclock as
> opposed to 8.7 seconds to tar up, so the patch degrades the
> performance by about 5%. Maybe we would want to revert that one
> as well.
Hmm. Rather than revert it outright, it might be better to make it use the
nicer parsing functions and "struct tree_desc".
It shouldn't look _that_ different from the "struct tree" version: instead
of doing
item = item->next;
it would do
update_tree_entry(tree);
instead.
Give me a minute, I'll send you patches.
Linus
next prev parent reply other threads:[~2006-01-31 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 19:04 [PATCH 0/3] Remove more parsers Daniel Barkalow
2006-01-29 19:04 ` [PATCH 1/3] Use struct tree in tar-tree Daniel Barkalow
2006-01-29 19:05 ` [PATCH 2/3] Use struct commit " Daniel Barkalow
2006-01-29 19:05 ` [PATCH 3/3] Use struct tree in diff-tree Daniel Barkalow
2006-01-31 16:53 ` Linus Torvalds
2006-01-31 21:20 ` Junio C Hamano
2006-01-31 21:49 ` Daniel Barkalow
2006-01-31 22:07 ` Linus Torvalds [this message]
2006-01-29 20:26 ` [PATCH 0/3] Remove more parsers Junio C Hamano
2006-01-29 22:05 ` Daniel Barkalow
2006-01-31 17:16 ` Linus Torvalds
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=Pine.LNX.4.64.0601311337500.7301@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).