Jeff King 2b8130c338 push: indicate partialness of error message
The existing message indicates that an error occured during
push, but it is unclear whether _any_ refs were actually
pushed (even though the status table above shows which were
pushed successfully and which were not, the message "failed
to push" implies a total failure). By indicating that "some
refs" failed, we hopefully indicate to the user that the
table above contains the details.

We could also put in an explicit "see above for details"
message, but it seemed to clutter the output quite a bit
(both on a line of its own, or at the end of the error line,
which inevitably wraps).

This could also be made more fancy if the transport
mechanism passed back more details on how many refs
succeeded and failed:

  error: failed to push %d out of %d refs to '%s'

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-02-19 20:44:47 -08:00
2007-06-07 00:04:01 -07:00
2007-11-11 12:10:35 -08:00
2008-02-15 23:01:49 -08:00
2008-02-17 00:20:38 -08:00
2008-01-23 21:37:12 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-15 21:23:47 -08:00
2008-02-17 00:20:38 -08:00
2007-05-30 15:03:50 -07:00
2008-01-16 15:35:35 -08:00
2007-06-07 00:04:01 -07:00
2008-01-16 15:35:35 -08:00
2007-11-09 00:21:44 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 15:35:35 -08:00
2008-01-16 15:35:35 -08:00
2007-12-04 17:16:33 -08:00
2008-01-16 15:35:35 -08:00
2007-09-26 02:27:06 -07:00
2007-09-26 02:27:06 -07:00
2008-02-06 14:02:41 -08:00
2007-12-05 17:57:11 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-15 23:06:57 -08:00
2008-01-04 16:05:23 -08:00
2007-06-07 00:04:01 -07:00
2007-12-16 12:50:08 -08:00
2007-11-14 14:15:40 -08:00
2008-02-03 16:01:27 -08:00
2007-11-17 21:39:37 -08:00
2007-11-28 17:06:57 -08:00
2007-10-26 23:17:23 -07:00
2008-02-17 00:20:38 -08:00
2006-09-27 23:59:09 -07:00
2007-11-14 14:04:19 -08:00
2008-02-05 23:31:17 -08:00
2007-10-03 04:28:24 -07:00
2007-10-26 23:27:23 -07:00
2008-01-26 10:52:40 -08:00
2007-12-13 23:04:26 -08:00
2007-06-07 00:04:01 -07:00
2007-12-13 23:04:26 -08: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-12-26 17:13:36 -08:00
2007-12-26 17:13:36 -08:00
2007-07-02 17:12:48 -07:00
2008-02-17 00:20:38 -08:00
2007-12-03 23:43:07 -08:00
2007-12-26 11:57:36 -08:00
2007-11-09 21:14:10 -08:00
2007-12-04 17:07:10 -08:00
2007-06-07 00:04:01 -07:00
2008-01-03 01:23:12 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2007-05-01 02:59:08 -07:00
2007-08-10 11:44:23 -07:00
2007-12-18 01:10:24 -08:00
2007-12-09 00:55:55 -08: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
No description provided
Readme 586 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%