Junio C Hamano 46220ca100 remote.c: Fix overtight refspec validation
We tightened the refspec validation code in an earlier commit ef00d15
(Tighten refspec processing, 2008-03-17) per my suggestion, but the
suggestion was misguided to begin with and it broke this usage:

    $ git push origin HEAD~12:master

The syntax of push refspecs and fetch refspecs are similar in that they
are both colon separated LHS and RHS (possibly prefixed with a + to
force), but the similarity ends there.  For example, LHS in a push refspec
can be anything that evaluates to a valid object name at runtime (except
when colon and RHS is missing, or it is a glob), while it must be a
valid-looking refname in a fetch refspec.  To validate them correctly, the
caller needs to be able to say which kind of refspecs they are.  It is
unreasonable to keep a single interface that cannot tell which kind it is
dealing with, and ask it to behave sensibly.

This commit separates the parsing of the two into different functions, and
clarifies the code to implement the parsing proper (i.e. splitting into
two parts, making sure both sides are wildcard or neither side is).

This happens to also allow pushing a commit named with the esoteric "look
for that string" syntax:

    $ git push ../test.git ':/remote.c: Fix overtight refspec:master'

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-03-22 23:46:17 -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
2008-02-29 00:00:09 -08:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-02-27 13:03:50 -08:00
2008-02-16 17:56:51 -08:00
2008-02-27 11:55:28 -08:00
2008-02-27 13:03:50 -08:00
2008-03-19 01:43:02 -07:00
2008-02-26 00:14:22 -08:00
2008-03-15 00:09:33 -07:00
2008-03-04 00:34:39 -08:00
2007-11-09 00:21:44 -08:00
2008-03-14 00:16:42 -07:00
2008-03-14 00:16:42 -07:00
2008-02-26 00:14:22 -08:00
2008-03-02 23:59:50 -08:00
2008-01-16 15:35:35 -08:00
2008-03-11 21:40:47 -07:00
2008-03-01 01:51:44 -08:00
2008-03-11 22:13:44 -07:00
2008-03-15 00:09:33 -07:00
2008-02-27 13:02:57 -08:00
2008-02-16 17:59:20 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-05 00:46:49 -08:00
2008-02-27 13:02:57 -08:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-03-12 21:10:00 -07:00
2008-03-12 23:47:31 -07:00
2008-03-16 01:03:16 -07:00
2008-03-15 01:10:53 -07:00
2008-03-08 19:43:21 -08:00
2008-02-27 15:37:57 -08:00
2008-02-05 23:31:17 -08:00
2008-03-15 00:09:33 -07:00
2008-03-15 00:09:33 -07:00
2008-03-17 00:52:19 -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-11-02 16:27:37 -07:00
2008-02-17 12:47:01 -08:00
2008-03-11 22:33:51 -07:00
2008-03-11 22:33:51 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-03-15 00:09:33 -07:00
2008-03-08 21:29:56 -08:00
2008-03-16 01:01:57 -07:00
2008-02-27 12:06:41 -08:00
2007-11-09 21:14:10 -08:00
2008-03-15 00:05:40 -07: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-03-02 15:11:07 -08:00
2007-12-09 00:55:55 -08:00
2008-02-25 23:57:35 -08:00
2008-02-27 15:37:57 -08: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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%