1
0
mirror of https://github.com/git/git.git synced 2025-04-19 14:37:09 +00:00
Eric Wong 5268f9edc3 svn: assume URLs from the command-line are URI-encoded
And then unescape them when writing to $GIT_CONFIG.

SVN has different rules for repository URLs (usually the root)
and for paths within that repository (below the HTTP layer).
Thus, for the request URI path at the HTTP level, the URI needs
to be encoded.  However, in the body of the HTTP request (the
with underlying SVN XML protocol), those paths should not be
URI-encoded[1].  For non-HTTP(S) requests, SVN appears to be
more flexible and will except weird characters in the URL as
well as URI-encoded ones.

Since users are used to using URLs being entirely URI-encoded,
git svn will now attempt to unescape the path portion of URLs
while leaving the actual repository URL untouched.

This change will be reflected in newly-created $GIT_CONFIG files
only.  This allows users to switch between svn(+ssh)://, file://
and http(s):// urls without changing the fetch/branches/tags
config keys.  This won't affect existing imports at all (since
things didn't work before this commit anyways), and will allow
users to force escaping into repository paths that look like
they're escaped (but are not).

Thanks to Mike Smullin for the original bug report and Björn
Steinbrink for summarizing it into testable cases for me.

[1] Except when committing copies/renames, see
    commit 29633bb91c7bcff31ff3bb59378709e3e3ef627d

Signed-off-by: Eric Wong <normalperson@yhbt.net>
2009-08-18 20:47:37 -07:00
2009-08-10 22:15:12 -07:00
2009-05-01 22:11:57 -07:00
2009-08-14 19:49:31 -07:00
2009-05-23 01:39:15 -07:00
2009-04-17 21:42:12 -07:00
2009-05-25 01:07:25 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2009-07-06 09:39:46 -07:00
2009-07-24 09:27:09 -07:00
2009-07-06 09:39:46 -07:00
2009-07-06 09:39:46 -07:00
2009-07-22 21:54:54 -07:00
2009-08-05 12:39:33 -07:00
2009-07-06 09:39:46 -07:00
2009-08-12 16:36:04 -07:00
2009-07-06 09:39:46 -07:00
2009-08-07 22:35:17 -07:00
2009-05-10 12:41:35 -07:00
2009-07-22 21:56:46 -07:00
2009-08-10 14:39:39 -07:00
2009-08-05 12:37:24 -07:00
2009-05-01 16:07:29 -07:00
2009-07-06 09:39:46 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-06-20 21:47:30 -07:00
2009-07-09 00:59:58 -07:00
2009-04-22 19:02:12 -07:00
2009-07-29 09:33:29 -07:00
2009-08-10 22:14:57 -07:00
2009-07-02 21:36:42 -07:00
2009-07-22 21:54:54 -07:00
2009-08-12 16:15:55 -07:00
2009-07-06 09:39:46 -07:00
2009-04-22 19:02:12 -07:00
2009-08-10 14:39:39 -07:00
2009-05-20 00:02:24 -07:00
2009-08-10 14:39:39 -07:00
2009-05-13 20:55:48 -07:00
2009-07-29 09:33:29 -07:00
2009-06-20 21:47:27 -07:00
2009-07-14 13:50:29 -07:00
2009-04-22 19:02:12 -07:00
2009-08-12 16:36:04 -07:00
2009-08-12 16:36:04 -07:00
2009-04-20 13:44:14 -07:00
2009-07-18 16:57:47 -07:00
2009-07-22 21:57:41 -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/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.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).

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 865 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%