Shawn O. Pearce d079837eee Lazily open pack index files on demand
In some repository configurations the user may have many packfiles,
but all of the recent commits/trees/tags/blobs are likely to
be in the most recent packfile (the one with the newest mtime).
It is therefore common to be able to complete an entire operation
by accessing only one packfile, even if there are 25 packfiles
available to the repository.

Rather than opening and mmaping the corresponding .idx file for
every pack found, we now only open and map the .idx when we suspect
there might be an object of interest in there.

Of course we cannot known in advance which packfile contains an
object, so we still need to scan the entire packed_git list to
locate anything.  But odds are users want to access objects in the
most recently created packfiles first, and that may be all they
ever need for the current operation.

Junio observed in b867092f that placing recent packfiles before
older ones can slightly improve access times for recent objects,
without degrading it for historical object access.

This change improves upon Junio's observations by trying even harder
to avoid the .idx files that we won't need.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-26 20:28:08 -07:00
2007-05-26 18:53:22 -07:00
2007-02-03 21:49:54 -08:00
2007-05-26 18:53:22 -07:00
2007-05-10 13:26:26 -07:00
2007-05-21 23:34:54 -07:00
2007-05-21 23:34:54 -07:00
2007-04-22 10:44:56 -07:00
2007-05-06 00:21:03 -07:00
2007-05-20 19:58:03 -07:00
2007-02-27 22:15:42 -08:00
2007-05-21 23:34:54 -07:00
2007-05-14 18:50:01 -07:00
2007-05-23 00:17:47 -07:00
2007-04-07 02:26:24 -07:00
2007-05-24 21:35:29 -07:00
2007-05-20 02:19:19 -07:00
2007-03-20 22:17:47 -07:00
2007-02-24 01:42:06 -08:00
2007-04-25 23:31:45 -07:00
2007-05-24 19:01:56 -07:00
2007-05-21 23:34:54 -07:00
2007-05-26 20:28:08 -07:00
2007-05-16 12:43:05 -07:00
2007-04-25 21:39:43 -07:00
2007-05-20 02:19:19 -07:00
2007-05-16 12:48:18 -07:00
2007-04-25 21:39:43 -07:00
2007-04-21 17:21:10 -07:00
2007-05-26 18:53:22 -07:00
2007-04-22 22:16:14 -07:00
2007-05-21 23:34:54 -07:00
2007-05-21 23:34:54 -07:00
2007-05-21 23:34:54 -07:00
2007-05-20 02:19:19 -07:00
2007-05-23 22:37:23 -07:00
2007-05-26 00:33:03 -07:00
2007-05-16 12:43:05 -07:00
2007-02-03 21:49:54 -08:00
2007-05-26 18:53:22 -07:00
2007-04-23 21:39:28 -07:00
2007-05-17 17:36:57 -07:00
2007-05-26 00:33:03 -07:00
2007-05-20 00:30:39 -07:00
2007-05-20 19:57:00 -07:00
2007-05-13 13:34:40 -07:00
2007-03-27 16:57:57 -07:00
2007-03-07 10:47:10 -08:00
2007-03-07 10:47:10 -08:00
2007-05-21 23:34:54 -07:00
2007-05-06 00:21:03 -07:00
2007-04-07 02:29:40 -07:00
2007-03-19 02:48:37 -07:00
2007-05-24 19:01:50 -07:00
2007-04-24 00:08:49 -07:00
2007-03-07 10:47:10 -08:00
2007-05-21 23:34:54 -07:00
2007-02-08 17:48:22 -08:00
2007-05-20 00:15:53 -07:00
2007-03-10 22:07:26 -08:00
2007-04-24 00:08:49 -07:00
2007-05-01 02:59:08 -07:00
2007-05-21 23:34:54 -07:00
2007-05-07 22:02:40 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%