Jeff King 12d4996622 clone: disconnect transport after fetching
The current code just leaves the transport in whatever state
it was in after performing the fetch.  For a non-empty clone
over the git protocol, the transport code already
disconnects at the end of the fetch.

But for an empty clone, we leave the connection hanging, and
eventually close the socket when clone exits. This causes
the remote upload-pack to complain "the remote end hung up
unexpectedly". While this message is harmless to the clone
itself, it is unnecessarily scary for a user to see and may
pollute git-daemon logs.

This patch just explicitly calls disconnect after we are
done with the remote end, which sends a flush packet to
upload-pack and cleanly disconnects, avoiding the error
message.

Other transports are unaffected or slightly improved:

 - for a non-empty repo over the git protocol, the second
   disconnect is a no-op (since we are no longer connected)

 - for "walker" transports (like HTTP or FTP), we actually
   free some used memory (which previously just sat until
   the clone process exits)

 - for "rsync", disconnect is always a no-op anyway

Signed-off-by: Jeff King <peff@peff.net>
Acked-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-09-02 18:39:02 -07:00
2009-03-02 18:28:06 -08:00
2008-12-17 21:56:48 -08:00
2009-02-10 21:32:10 -08:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-08-28 20:50:10 -07:00
2008-09-10 15:00:17 -07:00
2008-08-03 14:14:10 -07:00
2009-01-28 11:33:51 -08:00
2008-09-15 23:11:35 -07:00
2009-02-19 23:44:07 -08:00
2008-09-25 09:39:24 -07:00
2009-01-25 17:13:29 -08:00
2009-01-25 17:13:29 -08:00
2009-02-10 21:32:10 -08:00
2009-01-28 11:33:03 -08:00
2009-05-05 22:49:43 -07:00
2009-01-05 13:01:01 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-17 18:30:41 -08:00
2008-11-02 16:36:40 -08:00
2009-01-25 17:13:34 -08:00
2009-02-10 21:32:10 -08:00
2008-11-11 14:49:50 -08:00
2008-02-25 23:57:35 -08:00
2009-02-26 23:06:38 -08:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2009-02-05 19:40:35 -08:00
2008-07-13 14:12:48 -07:00
2009-04-05 01:16:31 -07:00
2009-05-03 16:54:14 -07:00
2008-09-25 08:00:28 -07:00
2009-04-28 00:46:25 -07:00
2008-09-07 23:52:16 -07:00
2008-12-07 15:13:02 -08:00
2008-11-23 19:23:34 -08:00
2008-10-25 12:09:31 -07:00
2009-03-07 11:22:42 -08:00
2008-07-21 19:11:50 -07:00
2009-02-10 22:26:20 -08:00
2009-02-10 22:26:20 -08:00
2009-05-03 16:54:14 -07:00
2009-02-10 22:26:37 -08:00
2008-07-21 19:11:50 -07:00
2007-11-09 21:14:10 -08: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
2007-05-01 02:59:08 -07:00
2008-10-09 11:26:17 -07:00
2009-04-20 13:44:14 -07:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -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/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 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%