Junio C Hamano d1d3d46146 Merge branch 'ab/ref-filter-no-contains'
"git tag/branch/for-each-ref" family of commands long allowed to
filter the refs by "--contains X" (show only the refs that are
descendants of X), "--merged X" (show only the refs that are
ancestors of X), "--no-merged X" (show only the refs that are not
ancestors of X).  One curious omission, "--no-contains X" (show
only the refs that are not descendants of X) has been added to
them.

* ab/ref-filter-no-contains:
  tag: add tests for --with and --without
  ref-filter: reflow recently changed branch/tag/for-each-ref docs
  ref-filter: add --no-contains option to tag/branch/for-each-ref
  tag: change --point-at to default to HEAD
  tag: implicitly supply --list given another list-like option
  tag: change misleading --list <pattern> documentation
  parse-options: add OPT_NONEG to the "contains" option
  tag: add more incompatibles mode tests
  for-each-ref: partly change <object> to <commit> in help
  tag tests: fix a typo in a test description
  tag: remove a TODO item from the test suite
  ref-filter: add test for --contains on a non-commit
  ref-filter: make combining --merged & --no-merged an error
  tag doc: reword --[no-]merged to talk about commits, not tips
  tag doc: split up the --[no-]merged documentation
  tag doc: move the description of --[no-]merged earlier
2017-04-11 00:21:50 -07:00
2017-03-06 11:19:09 -08:00
2017-02-16 14:45:13 -08:00
2016-10-20 09:33:17 -07:00
2017-03-17 13:50:25 -07:00
2017-03-26 15:34:44 -07:00
2017-03-24 13:31:01 -07:00
2017-03-06 11:19:09 -08:00
2016-02-22 14:51:09 -08: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
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2017-01-25 14:42:37 -08:00
2016-08-12 09:47:37 -07:00
2017-03-10 13:24:24 -08:00
2016-05-09 12:29:08 -07:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2016-10-27 14:58:50 -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
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-02-16 14:45:12 -08:00
2016-12-19 14:45:35 -08:00
2017-03-24 12:59:15 -07:00
2017-02-15 12:54:19 -08:00
2017-03-17 12:18:41 -07: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
2017-02-20 01:11:26 -08: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
2016-12-07 11:31:59 -08:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-09-26 16:09: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
2016-09-29 15:42:18 -07:00
2017-01-30 14:17:00 -08:00
2017-03-28 14:05:59 -07:00
2016-10-17 13:25:21 -07:00
2017-03-13 14:39:36 -07:00
2017-03-10 13:24:24 -08:00
2017-01-30 14:17:00 -08:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-03-17 13:50:25 -07:00
2017-03-28 13:54:14 -07:00
2017-03-22 15:41:21 -07:00
2016-04-25 15:17:15 -07:00
2017-03-17 13:50:25 -07:00
2016-07-14 15:50:41 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:46 -07:00
2016-07-01 15:09:10 -07:00
2016-08-05 09:28:17 -07:00
2016-09-29 15:42:18 -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
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%