Jeff King 4eb707ebd6 rev-list: allow commit-only bitmap traversals
Ever since we added reachability bitmap support, we've been able to use
it with rev-list to get the full list of objects, like:

  git rev-list --objects --use-bitmap-index --all

But you can't do so without --objects, since we weren't ready to just
show the commits. However, the internals of the bitmap code are mostly
ready for this: they avoid opening up trees when walking to fill in the
bitmaps. We just need to actually pass in the rev_info to
traverse_bitmap_commit_list() so it knows which types to bother
triggering our callback for.

For completeness, the perf test now covers both the existing --objects
case, as well as the new commits-only behavior (the objects one got way
faster when we introduced bitmaps, but obviously isn't improved now).

Here are numbers for linux.git:

  Test                         HEAD^               HEAD
  ------------------------------------------------------------------------
  5310.7: rev-list (commits)   8.29(8.10+0.19)       1.76(1.72+0.04) -78.8%
  5310.8: rev-list (objects)   8.06(7.94+0.12)       8.14(7.94+0.13) +1.0%

That run was cheating a little, as I didn't have any commit-graph in the
repository, and we'd built it by default these days when running git-gc.
Here are numbers with a commit-graph:

  Test                         HEAD^               HEAD
  ------------------------------------------------------------------------
  5310.7: rev-list (commits)   0.70(0.58+0.12)     0.51(0.46+0.04) -27.1%
  5310.8: rev-list (objects)   6.20(6.09+0.10)     6.27(6.16+0.11) +1.1%

Still an improvement, but a lot less impressive.

We could have the perf script remove any commit-graph to show the
out-sized effect, but it probably makes sense to leave it in what would
be a more typical setup.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-02-14 10:46:22 -08:00
2019-12-06 15:09:21 -08:00
2019-12-01 09:04:35 -08: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
2019-08-19 15:04:58 -07:00
2019-10-15 13:48:02 +09:00
2019-07-19 11:30:20 -07:00
2019-07-09 15:25:44 -07:00
2019-07-09 15:25:44 -07:00
2020-01-06 14:17:51 -08:00
2019-12-25 11:21:58 -08:00
2019-11-10 16:00:54 +09:00
2019-11-22 16:11:44 +09:00
2019-12-06 16:31:39 +01:00
2019-12-01 09:04:36 -08:00
2019-12-06 16:31:39 +01:00
2019-11-13 11:48:47 +09:00
2019-12-01 09:04:36 -08:00
2019-11-10 16:00:54 +09:00
2019-07-09 15:25:43 -07:00
2019-05-05 15:20:10 +09:00
2019-12-05 12:52:43 -08:00
2019-12-16 13:08:39 -08:00
2019-10-15 13:48:02 +09:00
2019-12-25 11:22:02 -08:00
2019-12-25 11:21:58 -08:00
2019-12-25 11:21:58 -08:00
2019-12-06 16:31:39 +01:00
2019-12-09 22:17:55 -08:00
2019-07-25 13:59:20 -07:00
2019-12-09 22:17:55 -08:00
2020-01-02 12:38:29 -08:00
2020-01-13 10:16:43 -08: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
2019-08-30 10:22:42 -07:00
2019-11-13 10:09:10 +09:00
2019-12-01 09:04:33 -08:00
2019-08-15 12:37:10 -07:00
2019-04-22 11:14:43 +09:00
2019-11-18 15:21:28 +09:00
2019-12-25 11:22:01 -08:00
2019-01-14 12:13:04 -08:00
2019-10-23 12:05:05 +09:00
2019-12-01 09:04:35 -08:00
2019-07-19 11:30:20 -07:00
2019-07-19 11:30:20 -07:00
2019-05-05 15:20:10 +09:00
2019-12-09 22:17:55 -08:00
2019-12-16 13:08:39 -08:00
2019-12-02 08:48:56 -08:00
2019-12-10 13:11:43 -08:00
2019-02-05 14:26:09 -08:00
2018-11-02 12:14:21 +09:00
2019-11-27 10:57:10 +09:00
2019-10-15 13:48:02 +09:00
2019-10-15 13:48:02 +09:00
2019-11-18 15:21:28 +09:00
2019-04-01 11:57:39 +09:00
2019-12-06 16:31:40 +01:00
2019-11-10 16:00:54 +09:00
2019-05-05 15:20:10 +09:00
2019-09-30 13:19:26 +09:00
2019-10-11 14:24:46 +09:00
2019-11-13 10:09:10 +09:00
2019-10-11 14:24:48 +09:00
2019-02-05 14:26:11 -08:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:30 +01:00
2019-12-06 16:31:30 +01:00
2018-12-09 12:37:32 +09:00
2019-09-05 14:10:18 -07:00
2019-05-13 23:50:35 +09:00
2019-11-18 15:21:29 +09:00
2019-08-13 12:21:33 -07:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:39 +01:00
2019-11-18 15:21:29 +09:00
2019-09-03 15:10:53 -07:00
2019-12-25 11:21:58 -08:00
2019-11-10 16:00:54 +09:00
2019-12-25 11:21:59 -08:00
2019-10-09 14:01:00 +09:00
2019-10-11 14:24:46 +09: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
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%