1
0
mirror of https://github.com/git/git.git synced 2025-03-21 22:53:07 +00:00
Jonathan Nieder b4b3360078 git-svn: strip off leading slashes on --trunk argument
The following command

 git svn clone \
	-r9500:10006 \
	svn://svn.debian.org/svn/pkg-games/packages \
	--trunk=/trunk/freedoom \
	--branches=/branches/freedoom \
	--tags=/tags/freedoom \
	freedoom.git.2009091

produces strange results:

With v1.6.3.3 (and perhaps earlier versions), this would fetch up to
and including r9978 (the last revision of the no_iwad_alternatives
branch before it was deleted), check it out, and prematurely declare
success, leaving out some commits to the trunk (r9984, r9985, r10006)
from after the branch was merged.

With v1.6.5-rc0~74 (svn: allow branches outside of refs/remotes,
2009-08-11) and later, this fetches up to and including r9978 and then
attempts a post-fetch checkout and fails.

 r9978 = 25f0920175c395f0f22f54ae7a2318147f745274
 (refs/remotes/no_iwad_alternatives)
 fatal: refs/remotes/trunk: not a valid SHA1
 update-ref refs/heads/master refs/remotes/trunk: command returned error: 128

Checking .git/config reveals

 fetch = packages//trunk/freedoom:refs/remotes/trunk

And with both 1.6.3.3 and 1.7.1, using --trunk=trunk/freedom without
the leading slash (/) works fine.

Moral: git-svn needs to scrub an initial / from $_trunk and related
arguments it receives.  Make it so.

Reported-by: Jon Dowland <jmtd@debian.org>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Acked-by: Eric Wong <normalperson@yhbt.net>
2010-06-14 04:44:02 +00:00
2010-06-13 11:22:39 -07:00
2010-06-13 11:21:30 -07:00
2010-05-28 16:59:42 -07:00
2010-06-13 11:22:42 -07:00
2010-02-07 15:52:28 -08:00
2010-06-13 11:22:42 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-04-01 23:53:54 -07:00
2010-04-01 23:53:54 -07:00
2010-05-08 22:33:08 -07:00
2010-03-20 11:29:35 -07:00
2010-06-13 11:21:25 -07:00
2010-05-07 09:34:27 -07:00
2010-05-28 15:08:27 -07:00
2010-02-11 23:06:32 -08:00
2010-05-25 10:49:54 -07:00
2010-04-03 12:28:44 -07:00
2010-05-11 23:04:47 -07:00
2010-06-13 11:21:30 -07:00
2010-06-13 11:20:46 -07:00
2010-04-01 23:58:30 -07:00
2010-04-01 23:58:30 -07:00
2010-04-19 22:16:35 -07:00
2010-06-13 11:21:00 -07:00
2010-05-08 22:58:36 -07:00
2010-06-07 22:15:31 -07:00
2010-03-24 16:26:43 -07:00
2010-03-24 16:26:43 -07:00
2010-06-06 18:42:12 -07:00
2010-05-04 15:38:58 -07:00
2010-04-12 21:45:17 -07:00
2010-04-12 21:45:17 -07:00
2010-01-24 17:35:58 -08:00
2010-06-13 11:22:05 -07:00
2010-04-02 00:05:31 -07:00
2010-04-10 00:43:59 -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-scm.com/
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 797 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%