Jeff King 2a0fe89a97 send-pack: tighten remote error reporting
Previously, we set all ref pushes to 'OK', and then marked
them as errors if the remote reported so. This has the
problem that if the remote dies or fails to report a ref, we
just assume it was OK.

Instead, we use a new non-OK state to indicate that we are
expecting status (if the remote doesn't support the
report-status feature, we fall back on the old behavior).
Thus we can flag refs for which we expected a status, but
got none (conversely, we now also print a warning for refs
for which we get a status, but weren't expecting one).

This also allows us to simplify the receive_status exit
code, since each ref is individually marked with failure
until we get a success response. We can just print the usual
status table, so the user still gets a sense of what we were
trying to do when the failure happened.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-11-18 02:34:52 -08:00
2007-06-07 00:04:01 -07:00
2007-11-05 22:03:47 -08:00
2007-11-11 15:00:05 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:42:23 -07:00
2007-10-19 01:18:55 -04:00
2007-05-30 15:03:50 -07:00
2007-11-02 16:42:23 -07:00
2007-06-07 00:04:01 -07:00
2007-11-01 13:47:47 -07:00
2007-06-07 00:04:01 -07:00
2007-11-12 00:14:15 -08:00
2007-11-05 18:57:58 -08:00
2007-09-19 03:22:30 -07:00
2007-11-09 00:21:44 -08:00
2007-11-04 01:11:17 -07:00
2007-03-20 22:17:47 -07:00
2007-11-11 15:19:24 -08:00
2007-11-05 12:25:42 -08:00
2007-09-26 02:27:06 -07:00
2007-09-26 02:27:06 -07:00
2007-08-10 23:17:46 -07:00
2007-06-07 00:04:01 -07:00
2007-10-30 16:08:40 -07:00
2007-10-30 16:08:40 -07:00
2007-06-07 00:04:01 -07:00
2007-11-01 13:47:47 -07:00
2007-08-14 22:34:58 -07:00
2007-06-07 00:04:01 -07:00
2007-10-29 17:03:11 -07:00
2007-08-10 23:17:46 -07:00
2007-06-13 02:02:10 -07:00
2007-10-18 03:45:05 -04:00
2007-10-03 03:05:32 -07:00
2007-11-09 00:21:44 -08:00
2007-11-07 17:12:53 -08:00
2007-10-03 03:05:58 -07:00
2007-10-26 23:17:23 -07:00
2007-11-09 00:21:44 -08:00
2007-11-09 00:21:44 -08:00
2007-10-31 12:20:05 -07:00
2007-09-19 03:22:30 -07:00
2007-08-13 23:34:38 -07:00
2007-11-11 15:00:05 -08:00
2007-10-02 17:35:29 -07:00
2007-10-03 04:28:24 -07:00
2007-10-26 23:27:23 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-11-02 16:27:37 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-10-30 16:08:40 -07:00
2007-07-02 17:12:48 -07:00
2007-10-18 03:11:17 -04:00
2007-09-05 11:29:33 -07:00
2007-11-09 00:17:52 -08:00
2007-11-09 21:14:10 -08:00
2007-10-15 22:31:47 -04:00
2007-11-09 21:14:10 -08:00
2007-07-11 13:52:16 -07:00
2007-10-29 12:53:54 -07:00
2007-06-07 00:04:01 -07:00
2007-09-18 17:42:17 -07:00
2007-05-01 02:59:08 -07:00
2007-10-21 01:59:42 -04:00
2007-06-07 00:04:01 -07:00
2007-06-22 23:19:43 -07:00
2007-08-10 11:44:23 -07:00
2007-10-30 16:08:40 -07:00
2007-06-07 00:04:01 -07:00
2007-09-19 03:22:30 -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/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
A fork of Git containing Windows-specific patches.
Readme 385 MiB
2025-08-19 03:50:05 -05:00
Languages
C 51.7%
Shell 37.4%
Perl 4.3%
Tcl 3.1%
Python 0.8%
Other 2.5%