On Tue, May 01, 2007 at 11:22:28AM -0400, Shawn O. Pearce wrote:
quoted text
> Chris Shoemaker <c.shoemaker@cox.net> wrote:
> > On Tue, May 01, 2007 at 11:21:14AM +0100, Andy Parkins wrote:
> > > Hello,
> > > 
> > > I've done this by hand as a proof of concept I suspect it would need loads of 
> > > work in git-svn to do it properly.  However, I thought I'd mention as part of 
> > > my "success with submodules" reports.
> > 
> > For my part, I wonder if it can be simplified somehow; and I suspect
> > it doesn't work well with svn:externals that specify a particular
> > revision.
> 
> Actually that is an interesting point that Chris makes.  Isn't the
> svn:externals property revision controlled on the parent directory?
> So each change to it is actually recorded in the revision history
> of the parent project.  

Yes and yes.

quoted text
> And if every svn:externals URL included the
> exact version of the other project to include, aren't svn:externals
> then more-or-less like the subproject link support, except they
> also include the URL?

Just to clarify, my point was just that Andy's setup seems to assume
that the externals don't specify a revision.  If they do, maybe
git-svn can map the externals into subprojects.  Is this what
you're thinking?

-chris

quoted text
> 
> -- 
> Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html