SZEDER Gábor 51b74b57ae t5536: simplify checking of messages output to stderr
Commit 2071e05ed2 ("t5536: new test of refspec conflicts when
fetching", 2013-10-30), introduced the verify_stderr() function
which was used to verify that certain fatal/warning messages were
issued by a given git command. In addition, verify_stderr() would
filter a specific "fatal: The remote end hung up unexpectedly"
message, which may, or may not, be present (depending on the
relative timing of the git-fetch and git-upload-pack processes).

The verify_stderr() function has seen several modifications, which
has introduced a couple of minor problems. For example, commit
1edbaac3bb ("tests: use test_i18n* functions to suppress false
positives", 2016-06-17) introduced an inappropriate test_i18ngrep
call and commit f096e6e826 ("fetch: improve the error messages
emitted for conflicting refspecs", 2013-10-30) included an
ineffective invocation of sort at the end of a grep pipeline.

Instead of fixing these minor problems in verify_stderr(), we take
the simpler approach of directly searching the error file, using
test_i18ngrep, for the specific message(s) we expect. (The only
minor downside is that we would not notice any new messages).

Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-02-28 09:45:07 -08:00
2017-11-21 14:07:50 +09:00
2018-01-21 21:14:25 -08:00
2018-01-15 07:47:30 +01:00
2017-07-06 18:14:44 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2018-01-10 14:01:25 -08:00
2017-11-15 12:14:28 +09:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-08-03 11:08:10 -07:00
2017-05-02 10:46:41 +09:00
2017-11-06 13:11:21 +09:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2017-11-08 11:34:00 +09:00
2017-12-12 10:39:43 -08:00
2017-06-24 14:28:41 -07:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2017-12-13 13:28:54 -08:00
2017-12-28 14:08:46 -08:00
2017-11-28 10:40:04 +09:00
2017-12-27 11:16:21 -08:00
2017-12-27 11:16:21 -08:00
2017-11-21 14:07:50 +09:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2018-01-21 21:14:25 -08:00
2017-11-28 13:41:50 +09:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2017-11-01 10:35:39 +09:00
2017-08-23 15:12:07 -07:00
2017-06-24 14:28:41 -07:00
2017-12-28 14:08:50 -08:00
2017-09-06 17:19:54 +09:00
2018-01-09 14:32:53 -08:00
2017-11-09 14:31:27 +09:00
2017-10-01 17:18:03 +09:00
2017-11-22 14:11:56 +09:00
2017-08-23 15:12:07 -07:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2017-10-28 10:18:40 +09:00
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2017-11-27 11:06:37 +09:00
2018-01-21 21:14:25 -08:00
2017-09-25 15:24:06 +09:00
2017-12-28 14:08:50 -08:00
2017-12-28 14:08:50 -08:00
2017-03-31 08:33:56 -07:00
2017-12-19 11:33:58 -08:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2017-06-24 14:28:41 -07:00
2017-08-26 22:55:04 -07:00
2017-06-24 14:28:41 -07:00
2017-11-21 14:07:50 +09:00
2017-12-06 09:23:44 -08:00
2017-11-06 14:24:27 +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.

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%