Linus Torvalds 17559a643e Do exact rename detection regardless of rename limits
Now that the exact rename detection is linear-time (with a very small
constant factor to boot), there is no longer any reason to limit it by
the number of files involved.

In some trivial testing, I created a repository with a directory that
had a hundred thousand files in it (all with different contents), and
then moved that directory to show the effects of renaming 100,000 files.

With the new code, that resulted in

	[torvalds@woody big-rename]$ time ~/git/git show -C | wc -l
	400006

	real    0m2.071s
	user    0m1.520s
	sys     0m0.576s

ie the code can correctly detect the hundred thousand renames in about 2
seconds (the number "400006" comes from four lines for each rename:

	diff --git a/really-big-dir/file-1-1-1-1-1 b/moved-big-dir/file-1-1-1-1-1
	similarity index 100%
	rename from really-big-dir/file-1-1-1-1-1
	rename to moved-big-dir/file-1-1-1-1-1

and the extra six lines is from a one-liner commit message and all the
commit information and spacing).

Most of those two seconds weren't even really the rename detection, it's
really all the other stuff needed to get there.

With the old code, this wouldn't have been practically possible.  Doing
a pairwise check of the ten billion possible pairs would have been
prohibitively expensive.  In fact, even with the rename limiter in
place, the old code would waste a lot of time just on the diff_filespec
checks, and despite not even trying to find renames, it used to look
like:

	[torvalds@woody big-rename]$ time git show -C | wc -l
	1400006

	real    0m12.337s
	user    0m12.285s
	sys     0m0.192s

ie we used to take 12 seconds for this load and not even do any rename
detection! (The number 1400006 comes from fourteen lines per file moved:
seven lines each for the delete and the create of a one-liner file, and
the same extra six lines of commit information).

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