Jonathan Tan eb398797cd connect: advertized capability is not a ref
When cloning an empty repository served by standard git, "git clone" produces
the following reassuring message:

	$ git clone git://localhost/tmp/empty
	Cloning into 'empty'...
	warning: You appear to have cloned an empty repository.
	Checking connectivity... done.

Meanwhile when cloning an empty repository served by JGit, the output is more
haphazard:

	$ git clone git://localhost/tmp/empty
	Cloning into 'empty'...
	Checking connectivity... done.
	warning: remote HEAD refers to nonexistent ref, unable to checkout.

This is a common command to run immediately after creating a remote repository
as preparation for adding content to populate it and pushing. The warning is
confusing and needlessly worrying.

The cause is that, since v3.1.0.201309270735-rc1~22 (Advertise capabilities
with no refs in upload service., 2013-08-08), JGit's ref advertisement includes
a ref named capabilities^{} to advertise its capabilities on, while git's ref
advertisement is empty in this case. This allows the client to learn about the
server's capabilities and is needed, for example, for fetch-by-sha1 to work
when no refs are advertised.

This also affects "ls-remote". For example, against an empty repository served
by JGit:

	$ git ls-remote git://localhost/tmp/empty
	0000000000000000000000000000000000000000        capabilities^{}

Git advertises the same capabilities^{} ref in its ref advertisement for push
but since it never did so for fetch, the client didn't need to handle this
case.  Handle it.

Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
Helped-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-09-09 13:40:36 -07:00
2016-05-10 11:19:07 -07:00
2016-08-12 09:17:51 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:20 -07:00
2016-06-12 01:25:58 +09:00
2016-04-25 15:17:15 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2014-07-13 18:59:05 -07:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2015-10-05 12:30:19 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2015-08-03 11:01:21 -07:00
2016-07-06 13:06:43 -07:00
2016-05-09 12:29:08 -07:00
2016-01-18 19:48:43 -08:00
2016-05-09 12:29:08 -07:00
2014-12-12 14:31:42 -08:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-04-03 10:29:22 -07:00
2016-05-23 14:54:29 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-05-17 14:38:34 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-08-12 09:17:51 -07:00
2016-05-17 14:38:28 -07:00
2016-02-22 14:51:09 -08:00
2016-05-17 14:38:32 -07:00
2014-10-20 12:23:48 -07:00
2016-05-17 14:38:28 -07:00
2016-05-06 14:45:44 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-07-28 11:28:32 -07:00
2016-05-23 14:54:38 -07:00
2016-04-25 15:17:15 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2014-12-22 12:27:30 -08:00
2014-09-02 13:28:44 -07:00
2016-02-22 10:40:35 -08:00

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 http://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-.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 http://news.gmane.org/gmane.comp.version-control.git/, http://marc.info/?l=git and other archival sites.

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 with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%