Taylor Blau 94fbd9149a t5318: test that '--stdin-commits' respects '--[no-]progress'
The following lines were not covered in a recent line-coverage test
against Git:

  builtin/commit-graph.c
  5b6653e5 244) progress = start_delayed_progress(
  5b6653e5 268) stop_progress(&progress);

These statements are executed when both '--stdin-commits' and
'--progress' are passed. Introduce a trio of tests that exercise various
combinations of these options to ensure that these lines are covered.

More importantly, this is exercising a (somewhat) previously-ignored
feature of '--stdin-commits', which is that it respects '--progress'.
Prior to 5b6653e523 (builtin/commit-graph.c: dereference tags in
builtin, 2020-05-13), dereferencing input from '--stdin-commits' was
done inside of commit-graph.c.

Now that an additional progress meter may be generated from outside of
commit-graph.c, add a corresponding test to make sure that it also
respects '--[no]-progress'.

The other location that generates progress meter output (from d335ce8f24
(commit-graph.c: show progress of finding reachable commits,
2020-05-13)) is already covered by any test that passes '--reachable'.

Signed-off-by: Taylor Blau <me@ttaylorr.com>
Acked-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-06-04 07:54:08 -07:00
2020-05-20 08:33:27 -07:00
2020-05-14 14:39:44 -07:00
2020-05-01 13:39:59 -07:00
2020-03-05 10:43:02 -08:00
2020-03-25 13:57:41 -07:00
2020-03-25 13:57:41 -07:00
2020-04-28 10:47:10 -07:00
2019-09-28 14:04:16 +09:00
2019-11-20 13:29:02 +09:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2020-03-30 10:59:08 -07:00
2020-02-19 09:37:15 -08:00
2020-04-16 15:38:06 -07:00
2020-05-14 14:39:44 -07:00
2020-05-14 14:39:44 -07:00
2020-04-10 09:28:02 -07:00
2019-07-09 15:25:44 -07:00
2020-03-24 15:04:44 -07:00
2020-04-22 13:42:49 -07:00
2020-05-24 19:39:36 -07:00
2020-05-13 12:19:18 -07:00
2019-12-01 09:04:36 -08:00
2019-11-10 16:00:54 +09:00
2019-12-25 11:21:58 -08:00
2020-03-10 11:41:40 -07:00
2020-05-13 12:19:18 -07:00
2020-05-01 13:39:56 -07:00
2020-03-24 15:04:43 -07:00
2019-07-25 13:59:20 -07:00
2020-05-31 23:03:57 -07:00
2020-05-13 12:19:18 -07:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2019-12-01 09:04:35 -08:00
2020-04-19 22:05:56 -07:00
2019-08-15 12:37:10 -07:00
2019-11-18 15:21:28 +09:00
2020-05-20 08:33:27 -07:00
2020-05-01 13:39:55 -07:00
2019-12-01 09:04:35 -08:00
2020-04-15 09:20:29 -07:00
2020-04-29 16:15:27 -07:00
2020-04-10 09:28:02 -07:00
2019-12-16 13:08:39 -08:00
2019-12-02 08:48:56 -08:00
2020-03-24 15:04:44 -07:00
2020-03-24 15:04:44 -07:00
2020-04-19 16:32:24 -07:00
2019-11-10 16:00:54 +09:00
2020-04-29 16:15:27 -07:00
2020-05-01 13:39:54 -07:00
2020-05-13 12:19:19 -07:00
2020-05-13 12:19:18 -07:00
2020-04-29 16:15:27 -07:00
2020-03-26 17:11:20 -07:00
2020-04-28 15:49:56 -07:00
2019-11-13 10:09:10 +09:00
2020-05-13 12:19:18 -07:00
2019-11-18 15:21:29 +09:00
2020-05-05 14:54:26 -07:00
2020-05-05 14:54:26 -07:00
2019-09-05 14:10:18 -07:00
2019-08-13 12:21:33 -07:00
2019-11-18 15:21:29 +09:00
2020-04-28 15:50:04 -07:00
2019-09-03 15:10:53 -07:00
2019-11-10 16:00:54 +09:00
2020-05-08 14:25:01 -07:00

Build status

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-<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).

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://lore.kernel.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
No description provided
Readme 694 MiB
Languages
C 50.5%
Shell 38.8%
Perl 4.4%
Tcl 3.2%
Python 0.8%
Other 2.1%