From: Steven Cole <elenstev@mesatop.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>, Greg KH <gregkh@suse.de>,
Git Mailing List <git@vger.kernel.org>,
linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Tue, 19 Apr 2005 17:41:57 -0600 [thread overview]
Message-ID: <200504191741.57626.elenstev@mesatop.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504191627420.2274@ppc970.osdl.org>
On Tuesday 19 April 2005 05:38 pm, Linus Torvalds wrote:
>
> On Tue, 19 Apr 2005, Steven Cole wrote:
> >
> > I wasn't complaining about the 4 minutes, just the lack of feedback
> > during the majority of that time. And most of it was after the last
> > patching file message.
>
> That should be exactly the thing that the new "read-tree -m" fixes.
>
> Before, when you read in a new tree (which is what you do when you update
> to somebody elses version), git would throw all the cached information
> away, and so you'd end up doing a "checkout-cache -f -a" that re-wrote
> every single checked-out file, followed by "update-cache --refresh" that
> then re-created the cache for every single file.
>
> With the new read-tree, the same sequence (assuming you have the "-m"
> flag to tell read-tree to merge the cache information) will now only write
> out and re-check the files that actually changed due to the update or
> merge.
>
> So that last phase should go from minutes to seconds - instead of checking
> 17,000+ files, you'd end up checking maybe a few hundred for most "normal"
> updates.
>
> For example, updating all the way from the git root (ie plain 2.6.12-rc2)
> to the current head, only 577 files have changed, and the rest (16,740)
> should never be touched at all.
>
> You can see why doing just the 577 instead of the full 17,317 might speed
> things up a bit ;)
>
> Linus
Cool. Petr, I hope this works like this with your tools tomorrow.
>
> PS. Of course, right now it probably does make sense to waste some time
> occasionally, and run "fsck-cache $(cat .git/HEAD)" every once in a while.
> Just in case..
>
>
Sounds like a good thing to schedule for $WEEHOUR.
Steven
next prev parent reply other threads:[~2005-04-19 23:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 4:39 [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2 Greg KH
2005-04-19 18:58 ` Greg KH
2005-04-19 19:40 ` Linus Torvalds
2005-04-19 19:47 ` Greg KH
2005-04-19 20:20 ` Linus Torvalds
2005-04-19 21:40 ` Greg KH
2005-04-19 22:00 ` Linus Torvalds
2005-04-19 22:27 ` Daniel Jacobowitz
2005-04-19 22:33 ` Greg KH
2005-04-19 23:04 ` Kenneth Johansson
2005-04-19 22:47 ` Linus Torvalds
2005-04-19 22:29 ` Martin Schlemmer
2005-04-19 22:43 ` Linus Torvalds
2005-04-19 23:11 ` Martin Schlemmer
2005-04-20 0:01 ` Jan-Benedict Glaw
2005-04-19 22:52 ` Lars Fenneberg
2005-04-19 22:39 ` Petr Baudis
2005-04-19 22:49 ` Linus Torvalds
2005-04-19 22:19 ` Steven Cole
2005-04-19 22:26 ` Petr Baudis
2005-04-19 22:45 ` Junio C Hamano
2005-04-19 22:58 ` Petr Baudis
2005-04-19 22:38 ` Linus Torvalds
2005-04-19 23:02 ` Petr Baudis
2005-04-19 23:04 ` Steven Cole
2005-04-19 23:16 ` Petr Baudis
2005-04-19 23:38 ` Linus Torvalds
2005-04-19 23:41 ` Steven Cole [this message]
2005-04-20 16:56 ` Zlatko Calusic
2005-04-20 17:15 ` 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=200504191741.57626.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=git@vger.kernel.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
--cc=torvalds@osdl.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).