1
0
mirror of https://github.com/git/git.git synced 2025-03-20 13:39:40 +00:00
Junio C Hamano 11cae066b2 upload-pack: feed "kind [clone|fetch]" to post-upload-pack hook
A request to clone the repository does not give any "have" but asks for
all the refs we offer with "want".  When a request does not ask to clone
the repository fully, but asks to fetch some refs into an empty
repository, it will not give any "have" but its "want" won't ask for all
the refs we offer.

If we suppose (and I would say this is a rather big if) that it makes
sense to distinguish these two cases, a hook cannot reliably do this
alone.  The hook can detect lack of "have" and bunch of "want", but there
is no direct way to tell if the other end asked for all refs we offered,
or merely most of them.

Between the time we talked with the other end and the time the hook got
called, we may have acquired more refs or lost some refs in the repository
by concurrent operations.  Given that we plan to introduce selective
advertisement of refs with a protocol extension, it would become even more
difficult for hooks to guess between these two cases.

This adds "kind [clone|fetch]" to hook's input, as a stable interface to
allow the hooks to tell these cases apart.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-08-28 22:39:24 -07:00
2009-08-23 17:18:52 -07:00
2009-05-01 22:11:57 -07:00
2009-08-23 17:19:06 -07:00
2009-05-23 01:39:15 -07:00
2009-05-31 17:03:40 -07:00
2008-07-19 11:25:51 -07:00
2008-07-19 11:17:43 -07:00
2009-05-25 01:07:25 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2007-06-07 00:04:01 -07:00
2009-07-24 09:27:09 -07:00
2009-07-06 09:39:46 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-08-21 18:47:53 -07:00
2009-07-22 21:54:54 -07:00
2009-08-05 12:39:33 -07:00
2009-07-06 09:39:46 -07:00
2009-08-12 16:36:04 -07:00
2009-07-06 09:39:46 -07:00
2009-08-07 22:35:17 -07:00
2009-08-21 18:47:53 -07:00
2009-02-13 17:27:58 -08:00
2009-07-22 21:56:46 -07:00
2009-08-21 18:47:53 -07:00
2009-08-05 12:37:24 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-07-06 09:39:46 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-06-20 21:47:30 -07:00
2009-07-09 00:59:58 -07:00
2008-11-02 16:36:40 -08:00
2009-08-21 18:47:53 -07:00
2009-04-22 19:02:12 -07:00
2008-07-13 14:12:48 -07:00
2009-08-21 20:16:10 -07:00
2009-08-21 18:47:53 -07:00
2008-09-25 08:00:28 -07:00
2009-07-02 21:36:42 -07:00
2009-07-22 21:54:54 -07:00
2009-08-12 16:15:55 -07:00
2008-09-07 23:52:16 -07:00
2009-08-18 23:33:16 -07:00
2009-07-06 09:39:46 -07:00
2009-04-22 19:02:12 -07:00
2009-08-21 18:47:53 -07:00
2008-10-25 12:09:31 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 20:16:10 -07:00
2009-06-20 21:47:27 -07:00
2009-02-14 21:27:35 -08:00
2009-08-21 18:47:53 -07:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-08-12 16:36:04 -07:00
2009-08-12 16:36:04 -07:00
2009-04-20 13:44:14 -07:00
2009-07-18 16:57:47 -07:00
2009-02-04 16:30:43 -08:00
2009-07-22 21:57:41 -07: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/gittutorial.txt to get started, then see
Documentation/everyday.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).

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 795 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%