Jeff King 5c885c1b53 test-lib: drop PID from test-results/*.count
Each test run generates a "count" file in t/test-results
that stores the number of successful, failed, etc tests.
If you run "t1234-foo.sh", that file is named as
"t/test-results/t1234-foo-$$.count"

The addition of the PID there is serving no purpose, and
makes analysis of the count files harder.

The presence of the PID dates back to 2d84e9f (Modify
test-lib.sh to output stats to t/test-results/*,
2008-06-08), but no reasoning is given there. Looking at the
current code, we can see that other files we write to
test-results (like *.exit and *.out) do _not_ have the PID
included. So the presence of the PID does not meaningfully
allow one to store the results from multiple runs anyway.

Moreover, anybody wishing to read the *.count files to
aggregate results has to deal with the presence of multiple
files for a given test (and figure out which one is the most
recent based on their timestamps!). The only consumer of
these files is the aggregate.sh script, which arguably gets
this wrong. If a test is run multiple times, its counts will
appear multiple times in the total (I say arguably only
because the desired semantics aren't documented anywhere,
but I have trouble seeing how this behavior could be
useful).

So let's just drop the PID, which fixes aggregate.sh, and
will make new features based around the count files easier
to write.

Note that since the count-file may already exist (when
re-running a test), we also switch the "cat" from appending
to truncating. The use of append here was pointless in the
first place, as we expected to always write to a unique file.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-08-30 12:08:58 -07:00
2016-05-10 11:19:07 -07:00
2016-08-12 09:17:51 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:20 -07:00
2016-06-12 01:25:58 +09:00
2016-04-25 15:17:15 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2015-10-05 12:30:19 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2016-07-06 13:06:43 -07:00
2016-05-09 12:29:08 -07:00
2016-01-18 19:48:43 -08:00
2016-05-09 12:29:08 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-04-03 10:29:22 -07:00
2016-05-23 14:54:29 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-05-17 14:38:34 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-08-12 09:17:51 -07:00
2016-05-17 14:38:28 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:32 -07:00
2016-05-17 14:38:28 -07:00
2016-05-06 14:45:44 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-07-28 11:28:32 -07:00
2016-05-23 14:54:38 -07:00
2016-04-25 15:17:15 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-02-22 10:40:35 -08: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 http://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 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.

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%