Ævar Arnfjörð Bjarmason 892e6f7ea6 test-lib: make test_expect_code a test command
Change test_expect_code to be a normal test command instead of a
top-level command.

As a top-level command it would fail in cases like:

    test_expect_code 1 'phoney' '
        foo && bar && (exit 1)
    '

Here the test might incorrectly succeed if "foo" or "bar" happened to
fail with exit status 1. Instead we now do:

    test_expect_success 'phoney' '
        foo && bar && test_expect_code 1 "(exit 1)"
    '

Which will only succeed if "foo" and "bar" return status 0, and "(exit
1)" returns status 1.  Note that test_expect_code has been made slightly
noisier, as it reports the exit code it receives even upon success.

Some test code in t0000-basic.sh relied on the old semantics of
test_expect_code to test the test_when_finished command. I've
converted that code to use an external test similar to the TODO test I
added in v1.7.3-rc0~2^2~3.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Acked-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-10-06 13:26:11 -07:00
2010-09-03 09:43: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-06-21 06:02:49 -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
2010-09-03 09:43:45 -07:00
2009-09-13 01:32:26 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-08-21 23:28:31 -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-21 06:02:49 -07:00
2009-12-13 23:40:24 -08:00
2010-06-13 20:02:50 -07:00
2010-09-29 13:21:24 -07:00
2010-09-29 10:39:53 -07:00
2010-06-30 15:49:18 -07:00
2010-08-22 20:18:37 -07:00
2010-06-21 06:02:44 -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
2010-01-12 01:06:09 -08: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 10:39:53 -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-01-20 20:28:50 -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-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
2010-07-25 21:57:23 -07:00
2010-05-24 16:48:32 -07:00
2010-08-16 18:28:27 -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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%