Derrick Stolee 22b2f3d2a3 negotiator: add have_sent() interface
In a future change, we will introduce a capability to choose specific commit
OIDs as 'have's in fetch negotiation, with the ability to have the
negotiator choose more 'have's to increase coverage beyond that required
core set. The negotiator works to avoid emitting 'have's that can reach each
other, but that logic is hidden beneath the negotiator's iterator function
pointer ('next'). We need a way to communicate to the negotiator that we
have picked a 'have' so it could incorporate that into its logic.

Add a have_sent() method to the fetch_negotiator interface. This is the
signal that allows the negotiator to track the commit as already shown and
can perform the proper bookkeeping to avoid emitting those objects or
anything they can reach.

For our non-trivial negotiators, it is sufficient to mark these commits as
common, so the implementation is quite simple. This logic will be exercised
in the next change.

Reviewed-by: Matthew John Cheetham <mjcheetham@outlook.com>
Signed-off-by: Derrick Stolee <stolee@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2026-05-20 11:33:24 +09:00
2026-02-03 09:41:52 -08:00
…
2026-03-09 14:36:55 -07:00
…
2026-03-20 09:31:04 +08:00
…
…
…
…
…
…
…
…
2025-12-07 07:28:13 +09:00
…
…
…
…
…
…
2026-01-09 18:36:16 -08:00
…
2026-02-07 17:41:03 -08:00
2026-02-09 12:09:09 -08:00
…
…
…
…
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
2026-03-10 14:23:24 -07:00
…
…
…
…
…
…
2026-03-10 14:23:24 -07:00
…
…
…
…
…
2026-02-19 13:23:41 -08:00
…
…
…
…
…
…
…
2026-02-17 13:30:41 -08:00
…
…
…
2026-03-16 10:48:15 -07:00
2026-02-23 13:21:19 -08:00
…
2026-03-16 10:48:15 -07:00
2025-11-25 12:15:59 -08:00
2025-11-25 12:15:59 -08:00
…
2026-02-23 13:21:18 -08:00
2026-03-16 10:48:15 -07:00
…
2026-03-12 14:09:07 -07:00
2026-03-12 14:09:07 -07:00
…
…
…
…
2026-02-20 08:13:58 -08:00
…
…
…
2026-02-08 15:03:06 -08:00
…
…
…
…
…
2026-03-09 14:36:55 -07:00
2025-11-04 07:48:07 -08:00
…
2026-03-10 14:23:18 -07:00
2026-03-09 14:36:55 -07:00
…
…
2026-02-05 15:42:01 -08:00
…
…
…
2026-03-09 14:36:55 -07:00
2026-01-22 10:58:14 -08:00
2026-03-19 09:54:56 -07:00
2026-03-06 13:02:20 -08:00
…
…
…
…
…
…
2025-12-29 22:02:54 +09:00
…
…
…
…
…
2026-05-20 11:33:23 +09:00
2026-05-20 11:33:23 +09:00
2026-01-09 18:36:17 -08:00
2026-01-09 18:36:17 -08:00
2026-03-09 14:36:55 -07:00
…
2026-02-08 15:16:49 -08:00
2026-02-08 15:16:49 -08:00
…
2025-12-07 07:28:11 +09:00
2025-11-12 14:04:04 -08: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
Languages
C 49.8%
Shell 39.8%
Perl 4.3%
Tcl 3%
Python 0.8%
Other 2.1%