Jeff King 7e27173ef9 t/lib-terminal: make TTY a lazy prerequisite
When lib-terminal.sh is sourced by a test script, we
immediately set up the TTY prerequisite. We do so inside a
test_expect_success, because that nicely isolates any
generated output.

However, this early test can interfere with a script that
later wants to skip all tests (e.g., t5541 then goes on to
set up the httpd server, and wants to skip_all if that
fails). TAP output doesn't let us skip everything after we
have already run at least one test.

We could fix this by reordering the inclusion of
lib-terminal.sh in t5541 to go after the httpd setup.  That
solves this case, but we might eventually hit a case with
circular dependencies, where either lib-*.sh include might
want to skip_all after the other has run a test.  So
instead, let's just remove the ordering constraint entirely
by doing the setup inside a test_lazy_prereq construct,
rather than in a regular test.  We never cared about the
test outcome anyway (it was written to always succeed).

Note that in addition to setting up the prerequisite, the
current test also defines test_terminal. Since we can't
affect the environment from a lazy_prereq, we have to hoist
that out. We previously depended on it _not_ being defined
when the TTY prereq isn't set as a way to ensure that tests
properly declare their dependency on TTY. However, we still
cover the case (see the in-code comment for details).

Reported-by: Jens Lehmann <Jens.Lehmann@web.de>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-14 15:23:49 -07:00
2014-02-13 13:41:53 -08:00
2013-09-09 14:50:36 -07:00
2013-06-10 10:55:42 -07:00
2013-12-09 14:54:48 -08:00
2013-07-22 16:06:49 -07:00
2013-07-22 16:06:49 -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
2013-12-09 14:54:47 -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
2014-02-13 13:41:53 -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-11-01 07:38:58 -07:00
2013-11-01 07:38:58 -07:00
2014-02-13 13:41:53 -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-10-31 13:46:03 -07:00
2013-10-31 13:48:26 -07:00
2013-10-31 13:48:32 -07:00
2013-07-22 11:23:35 -07:00
2013-06-20 16:02:18 -07:00
2013-12-09 14:54:48 -08: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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%