Jonathan Tan 9c1e657a8f fetch: teach independent negotiation (no packfile)
Currently, the packfile negotiation step within a Git fetch cannot be
done independent of sending the packfile, even though there is at least
one application wherein this is useful. Therefore, make it possible for
this negotiation step to be done independently. A subsequent commit will
use this for one such application - push negotiation.

This feature is for protocol v2 only. (An implementation for protocol v0
would require a separate implementation in the fetch, transport, and
transport helper code.)

In the protocol, the main hindrance towards independent negotiation is
that the server can unilaterally decide to send the packfile. This is
solved by a "wait-for-done" argument: the server will then wait for the
client to say "done". In practice, the client will never say it; instead
it will cease requests once it is satisfied.

In the client, the main change lies in the transport and transport
helper code. fetch_refs_via_pack() performs everything needed - protocol
version and capability checks, and the negotiation itself.

There are 2 code paths that do not go through fetch_refs_via_pack() that
needed to be individually excluded: the bundle transport (excluded
through requiring smart_options, which the bundle transport doesn't
support) and transport helpers that do not support takeover. If or when
we support independent negotiation for protocol v0, we will need to
modify these 2 code paths to support it. But for now, report failure if
independent negotiation is requested in these cases.

Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-05-05 10:41:29 +09:00
2021-04-02 14:43:14 -07:00
2021-04-07 16:54:08 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2020-12-08 15:11:21 -08:00
2021-03-08 09:56:34 -08:00
2021-01-21 15:50:00 -08:00
2020-12-08 15:11:17 -08:00
2019-09-28 14:04:16 +09:00
2021-03-13 16:00:09 -08:00
2021-03-30 14:35:37 -07:00
2019-11-18 15:21:28 +09:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2020-09-02 14:39:25 -07:00
2019-07-09 15:25:44 -07:00
2020-11-18 13:32:53 -08:00
2021-03-13 16:00:09 -08:00
2020-08-11 18:04:11 -07:00
2021-03-13 16:00:09 -08:00
2021-01-23 17:14:07 -08:00
2020-08-10 10:23:57 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-01-25 14:19:19 -08:00
2021-04-02 14:43:14 -07:00
2021-02-17 17:21:40 -08:00
2020-07-06 22:09:13 -07:00
2020-08-24 14:54:31 -07:00
2021-04-02 14:43:14 -07:00
2020-11-12 09:40:06 -08:00
2021-03-13 16:00:09 -08:00
2019-05-05 15:20:10 +09:00
2021-03-13 16:00:09 -08:00
2021-02-25 16:43:30 -08:00
2021-04-08 13:23:26 -07:00
2020-07-30 19:18:06 -07:00
2020-07-28 15:02:17 -07:00
2021-03-13 16:00:09 -08:00
2020-03-24 15:04:43 -07:00
2021-03-26 14:49:41 -07:00
2021-02-12 14:21:04 -08:00
2020-07-30 19:18:06 -07:00
2019-11-18 15:21:28 +09:00
2021-03-22 14:00:23 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-02-22 12:07:40 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2019-11-18 15:21:28 +09:00
2021-02-17 17:21:40 -08:00
2021-04-08 13:23:26 -07:00
2021-04-08 13:23:26 -07:00
2021-03-30 14:35:37 -07:00
2021-04-08 13:23:25 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-04-08 13:23:25 -07:00
2021-04-08 13:23:25 -07:00
2021-04-08 13:23:25 -07:00
2021-04-08 13:23:25 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2019-12-16 13:08:39 -08:00
2021-03-22 14:00:24 -07:00
2021-03-22 14:00:24 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2020-03-24 15:04:44 -07:00
2020-03-24 15:04:44 -07:00
2021-03-13 16:00:09 -08:00
2021-03-19 15:25:38 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2021-02-05 16:40:45 -08:00
2020-12-14 10:21:36 -08:00
2020-10-27 15:09:50 -07:00
2021-03-26 14:49:41 -07:00
2021-03-13 16:00:09 -08:00
2021-02-17 17:21:40 -08:00
2021-03-13 16:00:09 -08:00
2020-04-29 16:15:27 -07:00
2021-03-13 16:00:09 -08:00
2021-03-24 14:36:27 -07:00
2021-03-13 16:00:09 -08:00
2021-03-13 16:00:09 -08:00
2020-07-28 15:02:17 -07:00
2021-03-13 16:00:09 -08:00
2020-08-11 18:04:11 -07:00
2019-11-13 10:09:10 +09:00
2019-11-18 15:21:29 +09:00
2021-03-13 16:00:09 -08:00
2020-07-30 19:18:06 -07:00
2020-07-30 19:18:06 -07:00
2019-09-05 14:10:18 -07:00
2021-01-04 15:23:08 -08:00
2020-07-28 15:02:17 -07:00
2019-11-10 16:00:54 +09:00
2021-02-09 14:14:34 -08:00
2020-11-02 13:17:46 -08:00
2021-03-13 16:00:09 -08:00
2021-02-16 09:41:32 -08:00
2021-03-13 16:00:09 -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.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
No description provided
Readme 581 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%