SZEDER Gábor 10c600172c t5310-pack-bitmaps: fix bogus 'pack-objects to file can use bitmap' test
The test 'pack-objects to file can use bitmap' added in 645c432d61
(pack-objects: use reachability bitmap index when generating
non-stdout pack, 2016-09-10) is silently buggy and doesn't check what
it's supposed to.

In 't5310-pack-bitmaps.sh', the 'list_packed_objects' helper function
does what its name implies by running:

  git show-index <"$1" | cut -d' ' -f2

The test in question invokes this function like this:

  list_packed_objects <packa-$packasha1.idx >packa.objects &&
  list_packed_objects <packb-$packbsha1.idx >packb.objects &&
  test_cmp packa.objects packb.objects

Note how these two callsites don't specify the name of the pack index
file as the function's parameter, but redirect the function's standard
input from it.  This triggers an error message from the shell, as it
has no filename to redirect from in the function, but this error is
ignored, because it happens upstream of a pipe.  Consequently, both
invocations produce empty 'pack{a,b}.objects' files, and the
subsequent 'test_cmp' happily finds those two empty files identical.

Fix these two 'list_packed_objects' invocations by specifying the pack
index files as parameters.  Furthermore, eliminate the pipe in that
function by replacing it with an &&-chained pair of commands using an
intermediate file, so a failure of 'git show-index' or the shell
redirection will fail the test.

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-08-14 08:55:30 -07:00
2018-06-18 10:18:45 -07:00
2018-05-30 14:04:08 +09:00
2018-06-19 02:19:42 +09:00
2018-05-30 14:04:07 +09:00
2018-06-01 15:06:37 +09:00
2018-05-23 14:38:17 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:05 +09:00
2018-06-01 15:06:37 +09:00
2018-05-30 14:04:07 +09:00
2018-06-13 12:50:46 -07:00
2018-05-30 14:04:08 +09:00
2018-06-01 15:06:37 +09:00
2018-05-30 14:04:10 +09:00
2018-06-18 11:23:22 -07:00
2018-05-30 14:04:10 +09:00
2018-05-21 23:55:12 -04:00
2018-06-18 10:18:41 -07:00
2018-06-21 10:00:06 -07:00
2018-06-01 15:06:37 +09:00
2018-06-01 15:06:37 +09:00
2018-05-30 21:51:28 +09:00
2018-05-23 14:38:13 +09:00
2018-06-18 11:23:24 -07:00
2018-05-30 14:04:07 +09:00
2018-05-23 14:38:16 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:10 +09:00
2018-06-01 15:06:37 +09:00
2018-05-29 17:10:05 +09:00
2018-05-30 14:04:07 +09:00
2018-05-23 14:38:13 +09:00
2018-05-30 14:04:10 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 21:51:28 +09:00
2018-06-04 21:39:50 +09:00
2018-05-22 14:28:26 +09:00
2018-05-30 14:04:05 +09:00
2018-05-30 14:04:10 +09:00
2018-05-30 14:04:11 +09:00
2018-05-30 14:04:07 +09:00
2018-06-01 15:06:37 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:10 +09:00
2018-05-30 14:04:10 +09:00
2018-05-23 14:38:13 +09:00
2018-05-30 21:51:28 +09:00
2018-05-29 17:10:05 +09:00
2018-05-29 17:10:05 +09:00
2018-05-23 14:38:13 +09:00
2018-05-30 14:04:10 +09:00

Git - fast, scalable, distributed revision control system

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.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.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).

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 https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
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%