Jonathan Nieder e674c17db2 test_terminal: ensure redirections work reliably
For terminal tests that capture output/stderr, the TTY prerequisite
warning does not quite work for commands like

	test_terminal foo >out 2>err

because the warning gets "swallowed" up by the redirection that's
supposed only to be done by the subcommand.

Even worse, the outcome depends on whether stdout was already a
terminal (in which case test_terminal is a noop) or not (in which case
test_terminal introduces a pseudo-tty in the middle of the pipeline).

	$ test_terminal.perl sh -c 'test -t 1 && echo >&2 YES' >out
	YES
	$ sh -c 'test -t 1 && echo >&2 YES' >out
	$

So:

 - use the test_terminal script even when running with "-v".

 - skip tests that require a terminal when the test_terminal
   script is unusable because IO::Pty is not installed.

 - write the "need to declare TTY prerequisite" message to fd 4,
   where it will be printed when running tests with -v, rather
   than being swallowed up by an unrelated redireciton.

Noticed-by: Tay Ray Chuan <rctay89@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-10-18 16:20:19 -07:00
2010-09-29 13:48:44 -07:00
2010-10-06 13:49:45 -07:00
2010-06-13 20:02:50 -07:00
2010-09-15 12:34:48 -07:00
2010-09-04 08:15:36 -07:00
2010-05-31 17:36:27 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-09-29 13:48:20 -07:00
2010-08-18 12:46:55 -07:00
2010-08-18 12:46:55 -07:00
2010-09-08 09:17:01 -07:00
2010-09-03 09:43:45 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-09-29 13:49:03 -07:00
2010-05-07 09:34:27 -07:00
2010-01-20 14:37:25 -08:00
2010-05-28 15:08:27 -07:00
2010-06-13 20:02:50 -07:00
2010-09-29 13:21:24 -07:00
2010-09-29 15:26:17 -07:00
2010-06-30 15:49:18 -07:00
2010-08-22 20:18:37 -07:00
2010-01-21 20:03:45 -08:00
2010-06-21 06:02:44 -07:00
2010-08-12 15:44:51 -07:00
2010-08-09 11:35:46 -07:00
2009-04-22 19:02:12 -07:00
2010-01-12 01:06:09 -08:00
2010-10-06 12:10:29 -07:00
2010-04-01 23:58:30 -07:00
2010-04-01 23:58:30 -07:00
2010-09-06 00:12:04 -07:00
2010-06-22 09:45:22 -07:00
2010-09-29 15:26:17 -07:00
2010-09-03 09:43:41 -07:00
2010-01-20 14:46:35 -08:00
2010-08-21 23:28:31 -07:00
2010-06-21 06:02:45 -07:00
2010-08-31 16:23:31 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-09-27 10:42:11 -07:00
2010-01-17 22:49:36 -08:00
2010-09-06 00:11:59 -07:00
2010-04-12 21:45:17 -07:00
2009-01-17 18:30:41 -08:00
2009-08-23 17:11:28 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:38 -07:00
2010-08-14 19:35:37 -07:00
2010-08-26 16:42:59 -07:00
2009-04-20 13:44:14 -07:00
2010-07-25 21:57:23 -07:00
2010-05-24 16:48:32 -07:00
2010-04-02 00:05:31 -07:00
2009-07-22 21:57:41 -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
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%