1
0
mirror of https://github.com/git/git.git synced 2025-04-15 00:55:57 +00:00
Nguyễn Thái Ngọc Duy e721c1544f checkout: avoid unnecessary match_pathspec calls
In checkout_paths() we do this

 - for all updated items, call match_pathspec
 - for all items, call match_pathspec (inside unmerge_cache)
 - for all items, call match_pathspec (for showing "path .. is unmerged)
 - for updated items, call match_pathspec and update paths

That's a lot of duplicate match_pathspec(s) and the function is not
exactly cheap to be called so many times, especially on large indexes.
This patch makes it call match_pathspec once per updated index entry,
save the result in ce_flags and reuse the results in the following
loops.

The changes in 0a1283b (checkout $tree $path: do not clobber local
changes in $path not in $tree - 2011-09-30) limit the affected paths
to ones we read from $tree. We do not do anything to other modified
entries in this case, so the "for all items" above could be modified
to "for all updated items". But..

The command's behavior now is modified slightly: unmerged entries that
match $path, but not updated by $tree, are now NOT touched.  Although
this should be considered a bug fix, not a regression. A new test is
added for this change.

And while at there, free ps_matched after use.

The following command is tested on webkit, 215k entries. The pattern
is chosen mainly to make match_pathspec sweat:

git checkout -- "*[a-zA-Z]*[a-zA-Z]*[a-zA-Z]*"

        before      after
real    0m3.493s    0m2.737s
user    0m2.239s    0m1.586s
sys     0m1.252s    0m1.151s

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-03-27 08:53:15 -07:00
2013-03-19 12:20:40 -07:00
2012-10-17 15:55:46 -07:00
2013-01-30 21:12:16 +11:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2013-03-01 13:17:18 -08:00
2012-10-29 03:08:30 -04:00
2013-01-23 21:19:10 -08:00
2012-10-29 03:08:30 -04:00
2013-03-19 12:20:40 -07:00
2013-02-26 09:16:58 -08:00
2013-02-17 15:25:52 -08:00
2013-01-23 21:19:10 -08:00
2013-03-21 14:02:27 -07:00
2012-11-28 13:52:54 -08:00
2013-03-19 12:20:40 -07:00
2013-02-04 10:25:30 -08:00
2013-03-18 15:01:19 -07:00
2013-03-11 13:00:16 -07:00
2013-02-11 14:33:04 -08:00
2013-01-20 17:06:53 -08:00
2013-03-17 00:11:11 -07:00
2013-03-21 14:02:19 -07:00
2012-10-17 22:42:40 -07:00
2012-10-29 03:08:30 -04:00
2013-02-05 16:13:32 -08:00
2013-02-17 15:25:57 -08:00
2013-03-18 15:01:19 -07:00
2013-03-21 14:02:27 -07:00
2013-01-20 17:06:53 -08:00
2013-02-27 09:47:28 -08:00
2013-01-16 12:48:22 -08:00
2013-01-16 12:48:22 -08:00
2013-03-21 14:06:55 -07:00
2013-01-23 21:19:10 -08:00
2013-03-21 14:02:27 -07:00
2013-03-21 14:06:55 -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 version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
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 (read
Documentation/SubmittingPatches for instructions on patch submission).
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://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them give a good reference for
project status, development direction and remaining tasks.
Description
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%