1
0
mirror of https://github.com/git/git.git synced 2025-04-21 12:17:17 +00:00
Thomas Rast 342e9ef2d9 Introduce a performance testing framework
This introduces a performance testing framework under t/perf/.  It
tries to be as close to the test-lib.sh infrastructure as possible,
and thus should be easy to get used to for git developers.

The following points were considered for the implementation:

1. You usually want to compare arbitrary revisions/build trees against
   each other.  They may not have the performance test under
   consideration, or even the perf-lib.sh infrastructure.

   To cope with this, the 'run' script lets you specify arbitrary
   build dirs and revisions.  It even automatically builds the revisions
   if it doesn't have them at hand yet.

2. Usually you would not want to run all tests.  It would take too
   long anyway.  The 'run' script lets you specify which tests to run;
   or you can also do it manually.  There is a Makefile for
   discoverability and 'make clean', but it is not meant for
   real-world use.

3. Creating test repos from scratch in every test is extremely
   time-consuming, and shipping or downloading such large/weird repos
   is out of the question.

   We leave this decision to the user.  Two different sizes of test
   repos can be configured, and the scripts just copy one or more of
   those (using hardlinks for the object store).  By default it tries
   to use the build tree's git.git repository.

   This is fairly fast and versatile.  Using a copy instead of a clone
   preserves many properties that the user may want to test for, such
   as lots of loose objects, unpacked refs, etc.

Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-17 08:21:22 -08:00
2012-02-14 12:57:18 -08:00
2012-02-12 22:42:35 -08:00
2012-02-14 09:56:23 -08:00
2012-01-03 13:48:00 -08:00
2012-01-31 22:24:23 -08:00
2011-12-13 22:53:08 -08:00
2012-01-03 13:48:00 -08:00
2011-10-21 16:04:32 -07:00
2012-02-14 12:57:18 -08:00
2012-01-06 12:44:07 -08:00
2012-02-10 12:53:55 -08:00
2012-01-08 15:08:03 -08:00
2011-12-16 22:33:40 -08:00
2012-01-29 13:18:53 -08:00
2012-02-12 19:24:47 -08:00
2012-02-14 09:53:38 -08:00
2012-01-08 15:07:20 -08:00
2011-12-19 16:06:41 -08:00
2011-12-19 16:06:41 -08:00
2012-02-05 23:53:21 -08:00
2012-01-06 12:44:07 -08:00
2012-01-06 12:44:07 -08:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-01-06 12:44:07 -08:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-02-12 19:50:39 -08:00
2012-02-12 19:50:39 -08:00
2012-02-06 00:03:18 -08:00
2011-10-26 16:16:29 -07:00
2011-11-12 22:27:38 -08:00
2012-01-31 22:01:14 -08:00
2011-12-19 16:05:16 -08:00
2011-12-19 16:05:16 -08:00
2011-12-11 23:16:24 -08:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -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/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. 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
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 866 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%