Jeff King a88dbd2f8c t0300: make "quit" helper more realistic
We test a toy credential helper that writes "quit=1" and confirms that
we stop running other helpers. However, that helper is unrealistic in
that it does not bother to read its stdin at all.

For now we don't send any input to it, because we feed git-credential a
blank credential. But that will change in the next patch, which will
cause this test to racily fail, as git-credential will get SIGPIPE
writing to the helper rather than exiting because it was asked to.

Let's make this one-off helper more like our other sample helpers, and
have it source the "dump" script. That will read stdin, fixing the
SIGPIPE problem. But it will also write what it sees to stderr. We can
make the test more robust by checking that output, which confirms that
we do run the quit helper, don't run any other helpers, and exit for the
reason we expected.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
2020-04-19 16:10:52 -07:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-03-15 15:00:46 -07:00
2018-05-22 14:25:26 +09:00
2018-03-06 14:54:07 -08:00
2018-03-06 14:54:07 -08:00
2018-05-22 14:25:26 +09:00
2018-02-13 10:17:12 -08:00
2018-02-13 10:17:12 -08:00
2018-03-06 14:54:07 -08:00
2018-03-06 14:54:07 -08:00
2018-02-13 13:39:08 -08:00
2019-12-06 16:27:18 +01:00
2019-12-06 16:27:18 +01:00
2018-02-13 13:39:04 -08:00
2018-02-15 14:55:43 -08:00
2018-02-02 11:28:41 -08:00
2018-02-02 11:28:41 -08:00
2018-03-06 14:54:07 -08:00
2018-02-15 14:55:43 -08:00
2018-05-22 14:25:26 +09:00
2018-02-22 10:08:05 -08:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2018-05-21 23:55:12 -04:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-02-13 10:17:12 -08:00
2018-03-06 14:54:07 -08:00
2018-03-21 11:30:12 -07:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2018-03-06 14:54:07 -08:00
2018-03-15 15:00:46 -07:00
2018-03-06 14:54:07 -08:00
2018-03-06 14:54:07 -08:00
2018-02-02 11:28:41 -08:00
2018-03-06 14:54:07 -08:00
2019-12-06 16:26:55 +01:00
2019-12-06 16:27:36 +01:00
2020-03-17 13:25:33 -07:00
2018-02-27 10:33:58 -08:00
2018-05-21 23:55:12 -04:00
2018-03-06 14:54:07 -08:00
2018-03-14 12:01:05 -07:00
2019-12-06 16:27:18 +01:00
2018-05-22 14:18:06 +09:00
2019-12-06 16:27:36 +01:00
2019-12-06 16:27:36 +01:00
2018-02-22 10:08:05 -08:00
2019-12-06 16:27:36 +01:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2019-12-06 16:27:18 +01:00
2019-12-06 16:27:36 +01:00
2018-03-29 15:39:59 -07:00
2018-05-22 14:15:14 +09:00
2018-05-21 23:50:11 -04:00
2018-02-22 10:08:05 -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 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.

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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%