Toon Claes 7fc4c80a86 revision: add Bloom check that includes parent directories
revs_maybe_changed_in_bloom() reports whether a commit may have changed
any of the paths in the pathspec. It uses bloom_filter_contains_vec(),
which requires all keys of a path's key vector to be present, so it only
answers for the paths themselves.

A caller may track more than those paths. git-last-modified(1) with
--show-trees reports the last modifying commit for the tree entries
containing the paths as well, up to the root. For a pathspec "a/b/c/"
that means it reports "a" and "a/b" next to "a/b/c" and its entries, and
those can each resolve to a different commit. A commit that only changed
"a/top" is the answer for "a", even though it touched nothing under
"a/b".

Such a caller needs to know whether the path, or any of the directories
leading up to it, may have changed. Add
revs_maybe_changed_in_bloom_with_parents(), which asks that question by
using bloom_filter_contains_any_vec() instead. A key vector holds a key
for the path and one for each of its leading directories, so looking up
any of them answers it.

There are no callers yet, one is added in a subsequent commit.

Signed-off-by: Toon Claes <toon@iotcl.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-08-07 11:32:57 -07:00
2026-07-06 07:21:57 -07:00
2026-07-16 23:05:48 -07:00
2026-02-03 09:41:52 -08:00
2026-07-15 13:24:18 -07:00
2026-07-16 23:05:47 -07:00
2026-04-09 17:25:36 -07:00
2026-07-16 23:05:48 -07:00
2026-05-21 12:06:48 +09:00
2025-12-07 07:28:13 +09:00
2026-02-07 17:41:03 -08:00
2026-05-21 12:06:48 +09:00
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
2026-06-08 00:21:35 +09:00
2026-06-15 07:41:59 -07:00
2026-06-05 22:27:24 +09:00
2026-05-30 07:07:27 +09:00
2026-07-16 23:05:47 -07:00
2026-05-30 07:07:27 +09:00
2026-03-23 08:33:10 -07:00
2026-07-06 15:50:25 -07:00
2026-06-18 09:46:56 -07:00
2026-05-14 15:59:25 +09:00
2026-05-14 15:59:25 +09:00
2026-06-15 07:42:00 -07:00
2026-07-16 23:05:47 -07:00
2026-07-16 23:05:47 -07:00
2026-07-15 13:24:19 -07:00
2026-02-17 13:30:41 -08:00
2026-07-06 15:50:21 -07:00
2026-06-15 07:42:00 -07:00
2026-07-15 13:24:18 -07:00
2026-07-15 13:24:18 -07:00
2025-11-25 12:15:59 -08:00
2025-11-25 12:15:59 -08:00
2026-05-15 04:50:45 +09:00
2026-05-15 04:50:45 +09:00
2026-07-15 13:24:18 -07:00
2026-07-06 15:50:21 -07:00
2026-05-30 07:07:27 +09:00
2026-07-06 15:50:23 -07:00
2026-06-09 10:04:50 +09:00
2026-05-19 12:14:03 +09:00
2026-05-19 12:14:03 +09:00
2026-03-23 21:27:17 -07:00
2026-07-06 15:50:25 -07:00
2026-07-15 13:24:19 -07:00
2026-07-15 13:24:19 -07:00
2026-07-15 13:24:19 -07:00
2026-07-06 15:50:24 -07:00
2026-06-09 10:04:50 +09:00
2026-06-09 10:04:50 +09:00
2026-05-13 00:48:42 +09:00
2026-07-16 23:05:47 -07:00
2026-05-30 07:07:27 +09:00
2026-01-09 18:36:17 -08:00
2026-02-08 15:16:49 -08:00
2026-02-08 15:16:49 -08:00

GitHub build status GitLab 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.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://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
No description provided
Readme 616 MiB
Languages
C 49.9%
Shell 39.5%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.2%