read-cache: verify skipHash index by stat data "git status" and other commands read and refresh the index without the lock, then write it only if repo_update_index_if_able() finds the file's trailing checksum unchanged, so they cannot undo an update made by another process in between. Since ee1f0c242e (read-cache: add index.skipHash config option, 2023-01-06), the trailer can be all zeros, and feature.manyFiles and Scalar turn that on. The check then passes for any index on disk, and a "git add" that lands between status reading the index and taking the lock is silently reverted. When the recorded checksum is null, check instead that the stat data of the index file is unchanged since it was read or written, apart from the ctime, which renaming the lockfile into place changes. Ignore core.checkStat and core.useNanosec here: a false match loses an update, while a false mismatch only skips an optional write. On Windows, which reports no inode numbers, this rests on the size and the mtime, so two same-size rewrites within one 100ns tick could still be missed. unpack_trees() builds a new index from the one it was given and copies its checksum, so copy the stat data along with it. Assisted-by: Claude Opus 5.5, Gemini 4 Argon Signed-off-by: Mihai Cosma <mcosma@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
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):