1
0
mirror of https://github.com/git/git.git synced 2025-03-20 11:03:26 +00:00
Jeff King 9a7bbd1dd1 clean up error conventions of remote.c:match_explicit
match_explicit is called for each push refspec to try to
fully resolve the source and destination sides of the
refspec.  Currently, we look at each refspec and report
errors on both the source and the dest side before aborting.

It makes sense to report errors for each refspec, since an
error in one is independent of an error in the other.
However, reporting errors on the 'dst' side of a refspec if
there has been an error on the 'src' side does not
necessarily make sense, since the interpretation of the
'dst' side depends on the 'src' side (for example, when
creating a new unqualified remote ref, we use the same type
as the src ref).

This patch lets match_explicit return early when the src
side of the refspec is bogus. We still look at all of the
refspecs before aborting the push, though.

At the same time, we clean up the call signature, which
previously took an extra "errs" flag. This was pointless, as
we didn't act on that flag, but rather just passed it back
to the caller. Instead, we now use the more traditional
"return -1" to signal an error, and the caller aggregates
the error count.

This change fixes two bugs, as well:

  - the early return avoids a segfault when passing a NULL
    matched_src to guess_ref()

  - the check for multiple sources pointing to a single dest
    aborted if the "err" flag was set. Presumably the intent
    was not to bother with the check if we had no
    matched_src. However, since the err flag was passed in
    from the caller, we might abort the check just because a
    previous refspec had a problem, which doesn't make
    sense.

    In practice, this didn't matter, since due to the error
    flag we end up aborting the push anyway.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-06-18 12:39:13 -07:00
2007-06-07 00:04:01 -07:00
2008-05-26 19:10:43 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-05-25 14:25:02 -07:00
2008-05-25 14:25:02 -07:00
2008-05-25 14:25:02 -07:00
2008-05-25 14:25:02 -07:00
2008-03-14 00:16:42 -07:00
2008-05-25 14:25:02 -07:00
2008-06-06 09:21:48 -07:00
2008-05-25 14:25:02 -07:00
2008-05-26 19:49:01 -07:00
2008-05-25 14:25:02 -07:00
2007-06-07 00:04:01 -07:00
2008-06-16 17:39:50 -07:00
2008-05-26 22:38:19 -07:00
2007-06-07 00:04:01 -07:00
2008-05-10 18:14:28 -07:00
2008-02-05 00:46:49 -08:00
2008-05-25 13:41:37 -07:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-06-08 14:27:46 -07:00
2008-05-27 22:34:19 -07:00
2008-06-07 11:45:48 -07:00
2008-05-25 14:25:02 -07:00
2008-05-06 16:50:17 -07:00
2008-06-15 13:43:32 -07:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-06-07 00:04:01 -07:00
2008-03-08 21:29:56 -08:00
2008-05-25 13:41:37 -07:00
2008-06-07 11:45:48 -07:00
2008-05-25 13:41:37 -07:00
2007-11-09 21:14:10 -08:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2007-05-01 02:59:08 -07:00
2008-05-25 13:41:37 -07:00
2008-03-02 15:11:07 -08:00
2008-05-25 14:25:02 -07:00
2008-05-25 14:25:02 -07:00
2008-03-14 00:16:42 -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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 795 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%