Subject: git-svn: Some svn:external properties are randomly ignored
Date: Fri, 25 Mar 2011 12:19:07 +0100
Package: git-svn
Version: 1:1.7.2.5-1
Severity: normal
When cloning a rather large repository of mine with
git svn clone svn+ssh://[email protected]/svn ggz-trunk
(public variant: svn://svn.ggzgamingzone.org/svn)
I only get two m4/ggz directories in trunk:
./trunk/playground/irc/m4/ggz
./trunk/base-libs/m4/ggz
However, there are more which are also found with git-svn show-externals:
/utils/m4/ggz
/txt-client/m4/ggz
etc.
To me it looks like a bug that git-svn doesn't clone these externalised
directories in all places.
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages git-svn depends on:
ii git 1:1.7.2.5-1 fast, scalable, distributed revisi
ii libsvn-perl 1.6.12dfsg-5 Perl bindings for Subversion
ii libterm-readkey-perl 2.30-4 A perl module for simple terminal
ii libwww-perl 5.836-1 Perl HTTP/WWW client/server librar
git-svn recommends no packages.
Versions of packages git-svn suggests:
pn git-doc <none> (no description available)
ii subversion 1.6.12dfsg-5 Advanced version control system
-- no debconf information
Acknowledgement sent
to Jonathan Nieder <[email protected]>:
Extra info received and forwarded to list. Copy sent to Gerrit Pape <[email protected]>.
(Sun, 27 Mar 2011 06:33:03 GMT) (full text, mbox, link).
Subject: Re: git-svn: Some svn:external properties are randomly ignored
Date: Sun, 27 Mar 2011 01:30:21 -0500
Hi Josef,
Josef Spillner wrote:
> When cloning a rather large repository of mine with
> git svn clone svn+ssh://[email protected]/svn ggz-trunk
> (public variant: svn://svn.ggzgamingzone.org/svn)
> I only get two m4/ggz directories in trunk:
> ./trunk/playground/irc/m4/ggz
> ./trunk/base-libs/m4/ggz
> However, there are more which are also found with git-svn show-externals:
> /utils/m4/ggz
> /txt-client/m4/ggz
> etc.
>
> To me it looks like a bug that git-svn doesn't clone these externalised
> directories in all places.
git svn doesn't actually do anything special with svn:externals at all;
the idea of the "git svn show-externals" command is that the user might
come up with something to do with them, perhaps using a wrapper script.
For example, something like
http://algorithm.com.au/blog/files/git-svn-svn-externals.php might work
well for you.
Now this doesn't mean some future version of "git svn" should not
support externals. But a generic solution would have to answer some
questions:
- does the user prefer to clone the repos referred to using svn or
"git svn"? If using "git svn", with what parameters?
- should the git history include the history of the subprojects,
or should they be automatically ignored in .git/info/exclude?
- does it make sense to be able to opt out of cloning some subset
of the subprojects?
- what should "git svn rebase" and "git svn dcommit" do with the
subproject state?
Please feel free to present your answers in the form of a patch to
git-svn.perl and submit to [email protected], cc-ing me and Eric
Wong <[email protected]>. :) [1] If you just want to experiment
and do not have a one-size-fits-all solution yet, no problem with that
--- a script for contrib/ or even some documentation on how to work
with externals would be welcome as well.
Sorry I cannot offer more.
Thanks for writing,
Jonathan
[1] Documentation/SubmittingPatches has more hints.
Changed Bug title to 'git svn: handle svn:externals somehow' from 'git-svn: Some svn:external properties are randomly ignored'
Request was from Jonathan Nieder <[email protected]>
to [email protected].
(Fri, 16 Dec 2011 14:00:03 GMT) (full text, mbox, link).