1
0
mirror of https://github.com/git/git.git synced 2025-04-11 10:36:29 +00:00
Jeff King a63c12c9be t0000: simplify HARNESS_ACTIVE hack
Commit 517cd55 set HARNESS_ACTIVE unconditionally in
sub-tests, because that value affects the output of
"--verbose". t0000 needs stable output from its sub-tests,
and we may or may not be running under a TAP harness.

That commit made the decision to always set the variable,
since it has another useful side effect, which is
suppressing writes to t/test-results by the sub-tests (which
would just pollute the real results).

Since the last commit, though, the sub-tests have their own
test-results directories, so this is no longer an issue. We
can now update a few comments that are no longer accurate
nor necessary.

We can also revisit the choice of HARNESS_ACTIVE. Since we
must choose one value for stability, it's probably saner to
have it off. This means that future patches could test
things like the test-results writing, or the "--quiet"
option, which is currently ignored when run under a harness.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-01-02 14:43:11 -08:00
2013-12-17 11:42:12 -08:00
2013-06-16 20:06:55 -07:00
2014-01-02 14:43:11 -08:00
2013-09-09 14:50:36 -07:00
2012-10-25 06:42:02 -04:00
2012-10-29 03:08:30 -04:00
2013-06-10 10:55:42 -07:00
2013-07-22 16:06:49 -07:00
2013-07-22 16:06:49 -07:00
2013-07-24 19:20:59 -07:00
2013-09-09 14:36:15 -07:00
2013-10-23 13:21:31 -07:00
2013-10-23 13:21:31 -07:00
2013-09-11 15:03:28 -07:00
2013-07-19 09:26:15 -07:00
2012-11-28 13:52:54 -08:00
2013-11-12 09:24:27 -08:00
2013-09-18 11:44:50 -07:00
2013-09-17 11:42:34 -07:00
2013-10-18 13:50:12 -07:00
2013-12-02 15:34:44 -08:00
2013-12-17 11:42:12 -08:00
2013-10-18 13:49:57 -07:00
2013-05-10 10:27:31 -07:00
2013-05-10 10:27:31 -07:00
2013-05-08 15:31:54 -07:00
2013-10-30 12:09:53 -07:00
2013-04-11 17:39:05 -07:00
2013-07-22 16:06:49 -07:00
2013-10-30 12:10:33 -07:00
2013-10-18 13:49:57 -07:00
2013-07-29 12:32:25 -07:00
2013-10-23 13:21:31 -07:00
2013-10-23 13:21:31 -07:00
2013-10-31 13:47:41 -07:00
2013-07-30 08:13:38 -07:00
2013-07-30 08:13:38 -07:00
2013-02-05 16:13:32 -08:00
2013-11-01 07:38:58 -07:00
2013-11-01 07:38:58 -07:00
2013-12-17 11:42:12 -08:00
2013-09-09 14:30:29 -07:00
2013-09-09 14:36:15 -07:00
2013-07-15 10:56:07 -07:00
2013-09-09 14:36:15 -07:00
2013-11-18 14:31:29 -08:00
2013-10-31 13:46:03 -07:00
2013-10-31 13:48:26 -07:00
2013-10-31 13:48:32 -07:00
2013-10-31 13:47:19 -07:00
2013-07-22 11:23:35 -07:00
2013-06-20 16:02:18 -07:00
2013-09-09 14:36:15 -07:00
2013-09-17 11:37:33 -07:00
2013-09-17 11:37:33 -07:00
2013-11-18 12:25:28 -08:00
2013-11-12 09:24:27 -08: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 828 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%