From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/2] Soem core git optimizations
Date: Sat, 10 May 2008 19:36:46 -0700 [thread overview]
Message-ID: <7v4p958t35.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LFD.1.10.0805090856350.3142@woody.linux-foundation.org
Linus Torvalds <torvalds@linux-foundation.org> writes:
> I notice that Junio merged my fnmatch-avoidance patch, but I have a few
> other optimizations that I track in my private tree that I have sent out
> but probably didn't get much attention. They do matter from a performance
> angle, even if not as much as avoiding fnmatch did.
> ...
> and while this probably doesn't matter on most loads, the reason I'm
> re-sending is that I think it's pretty solid and core code. I've been
> running with both of these patches (and some others) rebased on top of
> Junio's tree for the last few weeks.
Unfortunately this seems to depend on stuff still in 'next', and a trivial
rebasing seems to break switching branches with "git checkout" in t4122
(switching from 'master' to 'test' will lose arch/i386/boot/Makefile).
I'll take a hint and merge the "case insensitive" and "diff-submodule"
series to 'master' and then apply these two --- the result does not have
the git-checkout breakage.
next prev parent reply other threads:[~2008-05-11 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:04 [PATCH 0/2] Soem core git optimizations Linus Torvalds
2008-05-09 16:11 ` [PATCH 1/2] Avoid some unnecessary lstat() calls Linus Torvalds
2008-05-09 16:21 ` [PATCH 2/2] Optimize symlink/directory detection Linus Torvalds
2008-05-11 2:36 ` Junio C Hamano [this message]
2008-05-11 2:42 ` [PATCH 0/2] Soem core git optimizations 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=7v4p958t35.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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).