Thomas Braun 45bc6f3d33 Config option to disable side-band-64k for transport
Since commit 0c499ea60f the send-pack builtin uses the side-band-64k
capability if advertised by the server.

Unfortunately this breaks pushing over the dump git protocol if used
over a network connection.

The detailed reasons for this breakage are (by courtesy of Jeff Preshing,
quoted from ttps://groups.google.com/d/msg/msysgit/at8D7J-h7mw/eaLujILGUWoJ):
----------------------------------------------------------------------------
MinGW wraps Windows sockets in CRT file descriptors in order to mimic the
functionality of POSIX sockets. This causes msvcrt.dll to treat sockets as
Installable File System (IFS) handles, calling ReadFile, WriteFile,
DuplicateHandle and CloseHandle on them. This approach works well in simple
cases on recent versions of Windows, but does not support all usage patterns.
In particular, using this approach, any attempt to read & write concurrently
on the same socket (from one or more processes) will deadlock in a scenario
where the read waits for a response from the server which is only invoked after
the write. This is what send_pack currently attempts to do in the use_sideband
codepath.
----------------------------------------------------------------------------

The new config option "sendpack.sideband" allows to override the side-band-64k
capability of the server, and thus makes the dump git protocol work.

Other transportation methods like ssh and http/https still benefit from
the sideband channel, therefore the default value of "sendpack.sideband"
is still true.

Signed-off-by: Thomas Braun <thomas.braun@byte-physics.de>
2018-09-05 09:24:32 -04:00
2018-08-28 16:21:17 -04:00
2018-06-19 02:19:42 +09:00
2018-08-02 13:54:58 -07:00
2018-09-04 14:31:40 -07:00
2018-09-03 22:47:41 +02:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 11:33:53 -07:00
2018-08-13 14:14:43 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 12:41:32 -07:00
2018-07-26 10:12:51 -07:00
2018-09-03 22:22:02 +02:00
2018-08-28 16:19:39 -04:00
2018-09-03 22:47:41 +02:00
2018-09-03 22:22:02 +02:00
2018-08-20 12:41:32 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-09-03 22:22:02 +02:00
2018-08-02 15:30:43 -07:00
2018-08-02 15:30:42 -07:00
2018-08-01 13:37:18 -07:00
2018-09-03 22:47:41 +02:00
2018-08-28 12:01:01 -07:00
2018-09-03 22:47:41 +02:00
2018-08-02 15:30:44 -07:00
2018-08-02 15:30:44 -07:00
2018-07-16 14:27:39 -07:00
2018-09-03 22:47:41 +02:00
2018-08-02 15:30:45 -07:00
2018-08-15 15:08:23 -07:00
2018-06-21 12:22:48 -07:00
2018-08-15 15:08:25 -07:00
2018-08-20 11:33:53 -07:00
2018-08-15 15:08:23 -07:00
2018-06-25 13:22:27 -07:00
2018-08-20 11:33:50 -07:00
2018-08-15 15:08:23 -07:00
2018-08-20 12:41:32 -07:00
2018-09-03 22:22:02 +02:00
2018-08-20 11:33:53 -07:00
2018-09-03 22:22:02 +02:00
2018-09-03 22:47:41 +02:00
2018-09-03 22:22:02 +02:00
2018-08-02 15:30:39 -07:00
2018-08-15 11:52:09 -07:00
2018-08-21 17:07:50 +02:00
2018-08-20 12:41:32 -07:00
2018-07-18 12:20:28 -07: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 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-.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://public-inbox.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 679 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%