Patrick Steinhardt f898661637 refs: expose peeled object ID via the iterator
Both the "files" and "reftable" backend are able to store peeled values
for tags in the respective formats. This allows for a more efficient
lookup of the target object of such a tag without having to manually
peel via the object database.

The infrastructure to access these peeled object IDs is somewhat funky
though. When iterating through objects, we store a pointer reference to
the current iterator in a global variable. The callbacks invoked by that
iterator are then expected to call `peel_iterated_oid()`, which checks
whether the globally-stored iterator's current reference refers to the
one handed into that function. If so, we ask the iterator to peel the
object, otherwise we manually peel the object via the object database.
Depending on global state like this is somewhat weird and also quite
fragile.

Introduce a new `struct reference::peeled_oid` field that can be
populated by the reference backends. This field can be accessed via a
new function `reference_get_peeled_oid()` that either uses that value,
if set, or alternatively peels via the ODB. With this change we don't
have to rely on global state anymore, but make the peeled object ID
available to the callback functions directly.

Adjust trivial callers that already have a `struct reference` available.
Remaining callers will be adjusted in subsequent commits.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-11-04 07:32:25 -08:00
2025-09-06 11:59:48 +02:00
2025-08-02 22:44:58 -07:00
2025-10-14 12:56:09 -07:00
2025-07-01 07:46:22 -07:00
2025-10-08 12:17:55 -07:00
2025-07-01 14:46:38 -07:00
2025-09-08 14:54:35 -07:00
2025-07-15 15:18:18 -07:00
2025-09-16 11:37:06 -07:00
2025-09-16 18:00:25 -07:00
2025-09-16 18:00:25 -07:00
2025-08-21 13:46:58 -07:00
2025-08-04 08:10:33 -07:00
2025-10-14 12:56:09 -07:00
2025-08-21 13:46:59 -07:00
2025-07-23 08:15:18 -07:00
2025-09-29 11:40:35 -07:00
2025-10-02 09:32:32 -07:00
2025-07-01 14:46:38 -07:00
2025-10-15 10:29:35 -07:00
2025-05-08 12:36:31 -07:00
2025-07-01 14:46:38 -07:00
2025-10-07 12:25:27 -07:00
2025-07-01 14:46:38 -07:00
2025-07-23 08:15:18 -07:00
2025-10-07 12:25:27 -07:00
2025-09-16 11:37:06 -07:00
2025-04-23 13:58:50 -07:00
2025-10-07 12:25:27 -07:00
2025-05-12 13:06:26 -07:00
2025-07-15 15:18:18 -07:00
2025-07-01 14:58:24 -07:00
2025-07-01 14:46:37 -07:00
2025-08-21 13:46:59 -07:00
2025-10-08 12:17:55 -07:00
2025-08-21 13:46:58 -07:00
2025-10-14 13:43:25 -07:00
2025-06-17 10:44:38 -07:00
2025-06-17 10:44:38 -07:00
2025-07-15 15:18:18 -07:00
2025-07-01 14:58:24 -07:00
2025-08-21 13:46:59 -07:00
2025-07-01 14:46:37 -07:00
2025-07-01 14:46:38 -07:00
2025-07-23 08:15:18 -07:00
2025-07-01 14:46:38 -07: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.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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 734 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%