Linus Torvalds 88ea8112b4 Optimize match_pathspec() to avoid fnmatch()
"git add *" is actually fundamentally different from "git add .", and
yeah, you should generally use the latter.

The reason? The argument list is actually something different from what
you think it is. For git, it's a "pathspec", so what actualy happens is
that in *both* cases, it will really traverse the whole tree, and then
match every file it finds against the pathspec.

So think of the arguments not as a file list, but as a random bunch of
patterns to match against the files you have!

Which is why the cost is actually approximately O(n*m), where "n" is the
size of the working tree, and "m" is the number of pathspecs.

So the reason "git add ." is fast is actually that "m" in that case is
just 1 (just one trivial pattern), and then "git add *" is slow because
"m" is large (lots of complicated patterns). In both cases, 'n' is the
same (== the whole set of files in your working tree).

Anyway, here's a trivial patch that doesn't change this fundamental fact,
but that avoids doing anything *expensive* until we've done some cheap
initial tests. It may or may not help your test-case, but it's pretty
simple and it matches the other git optimizations in this area (ie
"conceptually handle the general case, but optimize the simple cases where
we can exit early")

Notice how this patch doesn' actually change the fundamental O(n^2)
behaviour, but it makes it much cheaper by generally avoiding the
expensive 'fnmatch' and 'strlen/strncmp' when they are obviously not
needed.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-04-26 17:48:17 -07:00
2008-04-22 00:10:20 -07:00
2008-04-25 12:17:45 -07:00
2008-04-04 22:38:32 -07:00
2008-04-22 00:10:20 -07:00
2008-04-25 12:17:45 -07:00
2008-02-29 00:00:09 -08:00
2008-04-16 00:45:52 -07:00
2008-02-27 13:03:50 -08:00
2008-04-19 21:09:54 -07:00
2008-02-27 13:03:50 -08:00
2008-03-19 01:43:02 -07:00
2008-03-14 00:16:42 -07:00
2008-03-14 00:16:42 -07:00
2008-04-24 22:40:02 -07:00
2008-02-26 00:14:22 -08:00
2008-03-02 23:59:50 -08:00
2008-01-16 15:35:35 -08:00
2008-03-26 00:10:55 -07:00
2008-03-01 01:51:44 -08:00
2008-04-13 12:11:11 -07:00
2008-02-16 17:59:20 -08:00
2008-04-09 01:25:28 -07:00
2008-04-09 01:09:12 -07:00
2008-02-05 00:46:49 -08:00
2008-02-27 13:02:57 -08:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-04-16 00:45:52 -07:00
2008-03-12 23:47:31 -07:00
2008-04-02 00:22:20 -07:00
2008-04-19 21:11:29 -07:00
2008-04-07 21:57:43 -07:00
2008-04-01 23:40:06 -07:00
2008-02-27 15:37:57 -08:00
2008-02-05 23:31:17 -08:00
2008-03-15 00:09:33 -07:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2008-02-17 12:47:01 -08:00
2008-04-16 18:23:54 -07:00
2008-03-08 21:29:56 -08:00
2008-04-20 16:03:40 -07:00
2008-03-15 00:05:40 -07:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2008-03-02 15:11:07 -08:00
2008-02-25 23:57:35 -08:00
2008-02-27 15:37:57 -08:00
2008-03-14 00:16:42 -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 637 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%