Jeff King 1a0962dee5 t/perf: fix regression in testing older versions of git
Commit 7501b59 (perf: make the tests work in worktrees,
2016-05-13) introduced the use of "git rev-parse --git-path"
in the perf-lib setup code. Because the to-be-tested version
of git is at the front of the $PATH when this code runs,
this means we cannot use modern versions of t/perf to test
versions of git older than v2.5.0 (when that option was
introduced).

This is a symptom of a more general problem. The t/perf
suite is essentially independent of git versions, and
ideally we would be able to run the most modern and complete
set of tests across many historical versions (to see how
they compare). But any setup code they run is therefore
required to use the lowest common denominator we expect to
test.

So let's introduce a new variable, $MODERN_GIT, that we can
use both in perf-lib and in the test setup to get a reliable
set of git features (we might change git and break some
tests, of course, but $MODERN_GIT is tied to the same
version of git as the t/perf scripts, so they can be fixed
or adjusted together).

This commit fixes the "--git-path" case, but does not
mass-convert existing setup code to use $MODERN_GIT. Most
setup code is fairly vanilla and will work with effectively
all versions. But now the tool is there to fix any other
issues we find going forward.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-06-22 13:47:16 -07:00
2016-05-03 14:52:30 -07:00
2016-05-10 13:46:57 -07:00
2016-02-22 14:51:09 -08:00
2016-04-25 13:36:26 -07:00
2016-04-25 15:17:15 -07:00
2016-02-22 14:51:09 -08:00
2014-07-28 10:14:33 -07:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-02-26 13:37:16 -08:00
2015-10-05 12:30:19 -07:00
2016-05-06 14:45:44 -07:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2016-05-10 13:40:29 -07:00
2016-02-26 13:37:23 -08:00
2016-01-18 19:48:43 -08:00
2014-12-12 14:31:42 -08:00
2016-02-26 13:37:16 -08:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2015-11-20 08:02:05 -05:00
2016-04-03 10:29:22 -07:00
2015-09-28 14:57:10 -07:00
2016-02-22 14:51:09 -08:00
2016-02-26 13:37:16 -08:00
2014-01-17 12:21:20 -08:00
2015-06-29 11:39:10 -07:00
2016-05-10 13:40:29 -07:00
2016-04-29 14:19:11 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:51:09 -08:00
2014-07-07 13:56:38 -07:00
2013-05-08 15:31:54 -07:00
2016-05-06 14:45:44 -07:00
2016-05-06 14:45:43 -07:00
2016-04-29 12:59:06 -07:00
2016-02-22 14:51:09 -08:00
2014-10-20 12:23:48 -07:00
2016-05-06 14:45:44 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2014-03-31 15:29:27 -07:00
2016-03-01 12:24:15 -08:00
2016-03-01 12:24:15 -08:00
2015-09-25 08:54:54 -07:00
2016-04-29 14:19:11 -07:00
2016-04-25 15:17:15 -07:00
2016-04-25 15:17:15 -07:00
2016-05-06 14:45:44 -07:00
2016-02-26 13:37:16 -08:00
2016-05-06 14:45:44 -07:00
2014-06-13 11:49:40 -07:00
2014-12-22 12:27:30 -08:00
2014-09-02 13:28:44 -07:00
2015-08-11 14:29:36 -07:00
2016-02-22 10:40:35 -08:00
2016-01-19 11:22:29 -08:00
2016-04-13 14:12:34 -07:00

Git - fast, scalable, distributed revision control system

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.

Many Git online resources are accessible from http://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.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).

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
No description provided
Readme 605 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%