Ævar Arnfjörð Bjarmason 674ad936bb grep: fix erroneously copy/pasted variable in check/assert pattern
Fix an erroneously copy/pasted check for the pcre2_jit_stack variable
to check pcre2_match_context instead. The former was already checked
in the preceding "if" statement.

This is a trivial and obvious error introduced in my commit
94da9193a6 ("grep: add support for PCRE v2", 2017-06-01).

In practice if pcre2_match_context_create() returned NULL we were
likely in a situation where malloc() was returning NULL, and were thus
screwed anyway, but if only the pcre2_match_context_create() call
returned NULL (through some transitory bug) PCRE v2 would just
allocate and supply its own context object when matching, and we'd run
normally at the trivial expense of not getting a slight speedup by
sharing the context object between successive matches.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-06-21 09:18:44 -07:00
2017-05-04 16:26:47 +09:00
2017-02-16 14:45:13 -08:00
2016-10-20 09:33:17 -07:00
2017-04-26 15:39:13 +09:00
2017-03-26 15:34:44 -07:00
2017-06-02 08:29:05 +09:00
2017-03-24 13:31:01 -07:00
2016-02-22 14:51:09 -08:00
2014-07-28 10:14:33 -07:00
2016-11-22 13:55:20 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2017-03-13 15:28:54 -07:00
2017-03-13 15:28:54 -07:00
2017-04-26 15:39:08 +09:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2017-04-19 21:37:13 -07:00
2017-01-25 14:42:37 -08:00
2016-08-12 09:47:37 -07:00
2017-03-31 08:33:56 -07:00
2017-06-02 08:29:05 +09:00
2017-04-26 15:39:10 +09:00
2016-05-09 12:29:08 -07:00
2014-12-12 14:31:42 -08:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2017-05-01 11:01:52 +09:00
2017-03-31 08:33:56 -07:00
2016-09-29 15:42:18 -07:00
2016-12-12 15:15:07 -08:00
2016-05-09 12:29:08 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-04-26 15:39:02 +09:00
2017-05-09 23:26:02 +09:00
2017-02-15 12:54:19 -08:00
2017-06-02 08:29:05 +09:00
2017-03-17 10:40:25 -07:00
2017-03-22 13:41:41 -07:00
2017-03-22 13:41:41 -07:00
2016-02-22 14:51:09 -08:00
2017-01-30 14:17:00 -08:00
2016-12-07 11:31:59 -08:00
2017-06-02 08:29:05 +09:00
2016-12-07 11:31:59 -08:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-03-31 20:57:18 -07:00
2017-01-30 14:17:00 -08:00
2017-02-08 15:39:55 -08:00
2017-02-08 15:39:55 -08:00
2017-01-30 14:17:00 -08:00
2017-03-28 14:05:59 -07:00
2017-03-10 13:24:24 -08:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-05-01 11:08:02 +09:00
2017-04-19 21:37:13 -07:00
2017-04-19 21:37:13 -07:00
2017-04-26 15:39:13 +09:00
2017-05-05 13:29:43 +09:00
2016-04-25 15:17:15 -07:00
2017-04-19 21:37:13 -07:00
2017-03-31 08:33:56 -07:00
2017-04-19 21:37:13 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2014-12-22 12:27:30 -08:00
2016-08-05 09:28:17 -07:00
2016-09-29 15:42:18 -07:00
2014-09-02 13:28:44 -07:00
2017-01-31 13:14:56 -08:00
2016-02-22 10:40:35 -08:00
2016-09-26 18:16:23 -07: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 603 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%