1
0
mirror of https://github.com/git/git.git synced 2025-04-13 00:23:16 +00:00
Shawn O. Pearce 767f176a1f Make git-fetch follow tags we already have objects for sooner
If autofollowing of tags is enabled, we see a new tag on the remote
that we don't have, and we already have the SHA-1 object that the
tag is peeled to, then we can fetch the tag while we are fetching
the other objects on the first connection.

This is a slight optimization for projects that have a habit of
tagging a release commit after most users have already seen and
downloaded that commit object through a prior fetch session. In
such cases the users may still find new objects in branch heads,
but the new tag will now also be part of the first pack transfer
and the subsequent connection to autofollow tags is not required.

Currently git.git does not benefit from this optimization as any
release usually gets a new commit at the same time that it gets a
new release tag, however git-gui.git and many other projects are
in the habit of tagging fairly old commits.

Users who did not already have the tagged commit still require
opening a second connection to autofollow the tag, as we are unable
to determine on the client side if $tag^{} will be sent to the
client during the first transfer or not.  Such computation must be
performed on the remote side of the connection and is deferred to
another series of changes.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-03-03 00:05:45 -08:00
2008-02-20 16:13:19 -08:00
2008-03-02 16:07:30 -08:00
2008-03-02 23:59:50 -08:00
2008-02-29 00:00:09 -08:00
2008-02-27 13:03:50 -08:00
2008-02-27 12:53:26 -08:00
2008-02-16 17:56:51 -08:00
2008-02-27 11:55:28 -08:00
2008-02-27 13:03:50 -08:00
2008-03-01 01:09:06 -08:00
2008-02-26 00:14:22 -08:00
2008-02-20 16:13:16 -08:00
2008-02-27 12:53:26 -08:00
2008-02-26 00:14:22 -08:00
2008-03-02 23:59:50 -08:00
2008-01-16 15:35:35 -08:00
2008-02-25 19:57:06 -08:00
2008-02-27 12:53:26 -08:00
2008-03-02 15:11:07 -08:00
2008-03-02 15:11:07 -08:00
2008-02-27 13:02:57 -08:00
2008-02-16 17:59:20 -08:00
2008-03-02 01:00:30 -08:00
2008-02-27 11:55:28 -08:00
2008-02-05 00:46:49 -08:00
2008-02-27 13:02:57 -08:00
2008-02-25 23:57:35 -08:00
2008-02-25 23:57:35 -08:00
2008-02-20 16:13:19 -08:00
2007-11-17 21:39:37 -08:00
2008-02-23 11:49:34 -08:00
2008-02-16 17:57:47 -08:00
2008-02-27 12:53:26 -08:00
2008-02-22 13:39:20 -08:00
2008-02-24 18:31:50 -08:00
2008-02-27 15:37:57 -08:00
2008-02-27 15:37:57 -08:00
2008-02-05 23:31:17 -08:00
2008-02-27 12:06:41 -08:00
2008-03-02 16:07:30 -08:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2007-12-13 23:04:26 -08:00
2008-02-25 23:57:35 -08:00
2008-02-17 12:47:01 -08:00
2008-02-27 13:03:50 -08:00
2007-12-26 17:13:36 -08:00
2007-12-26 17:13:36 -08:00
2008-02-27 12:53:26 -08:00
2008-03-02 23:59:50 -08:00
2008-02-27 23:37:39 -08:00
2008-02-27 13:03:50 -08:00
2008-02-19 01:04:32 -08:00
2008-02-27 12:06:41 -08:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2008-03-02 15:11:07 -08:00
2008-02-27 12:53:26 -08:00
2007-12-09 00:55:55 -08:00
2008-02-25 23:57:35 -08:00
2008-02-27 15:37:57 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, 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

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.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

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. 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
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
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 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%