Jeff King ceacd91a06 t7502: drop confusing test_might_fail call
In t7502.20, we run "git commit" and check that it warns us
that the author and committer identity are not the same
(this is always the case in the test environment, since we
set up the idents differently).

Instead of actually making a commit, we have a clean index,
so the "git commit" we run will fail. This is marked as
might_fail, which is not really correct; it will always fail
since there is nothing to commit.

However, the only reason not to do a complete commit would
be to see the intermediate state of the COMMIT_EDITMSG file
when the commit is not completed. We don't need to care
about this, though; even a complete commit will leave
COMMIT_EDITMSG for us to view.  By doing a real commit and
dropping the might_fail, we are more robust against other
unforeseen failures of "git commit" that might influence our
test result.

It might seem less robust to depend on the fact that "git
commit" leaves COMMIT_EDITMSG in place after a successful
commit. However, that brings this test in line with others
parts of the script, which make the same assumption.
Furthermore, if that ever does change, the right solution is
not to prevent commit from completing, but to set EDITOR to
a script that will record the contents we see. After all,
the point of these tests is to check what the user sees in
their EDITOR, so that would be the most direct test. For
now, though, we can continue to use the "shortcut" that
COMMIT_EDITMSG is left intact.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-07-26 14:23:35 -07:00
2012-07-23 20:56:47 -07:00
2012-07-23 21:02:06 -07:00
2012-04-02 15:06:25 -07:00
2012-07-13 15:37:04 -07:00
2012-07-15 21:39:17 -07:00
2012-07-24 14:05:08 -07:00
2011-03-17 15:30:49 -07:00
2011-10-21 16:04:32 -07:00
2012-07-23 20:55:21 -07:00
2012-05-03 15:13:31 -07:00
2012-07-22 12:55:07 -07:00
2012-07-22 12:56:27 -07:00
2012-07-04 23:40:12 -07:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2009-06-18 09:22:46 -07:00
2012-07-23 20:56:03 -07:00
2011-09-19 20:46:48 -07:00
2012-07-15 21:38:32 -07:00
2012-07-15 21:38:42 -07:00
2012-07-23 21:02:06 -07:00
2012-06-25 11:55:51 -07:00
2012-04-06 10:15:11 -07:00
2012-06-03 13:11:34 -07:00
2012-05-03 15:13:31 -07:00
2011-12-19 16:06:41 -08:00
2012-03-28 08:47:23 -07:00
2012-05-29 13:09:13 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2012-07-23 20:56:47 -07:00
2012-01-06 12:44:07 -08:00
2011-08-22 10:07:07 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-04-27 09:26:38 -07:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-05-29 13:09:02 -07:00
2012-04-10 15:55:55 -07:00
2012-07-22 13:07:40 -07:00
2012-07-22 12:55:07 -07:00
2012-06-01 13:28:19 -07:00
2012-07-22 12:55:07 -07:00
2012-07-22 12:55:07 -07:00
2009-08-23 17:11:28 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07:00
2012-07-08 22:03:46 -07:00
2012-07-08 22:03:46 -07:00
2012-06-03 13:11:52 -07:00
2012-06-03 13:11:52 -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 (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://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%