git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Shoemaker <c.shoemaker@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: svn:externals using git submodules
Date: Tue, 1 May 2007 11:36:26 -0400	[thread overview]
Message-ID: <20070501153626.GA21182@pe.Belkin> (raw)
In-Reply-To: <20070501152228.GF5942@spearce.org>

On Tue, May 01, 2007 at 11:22:28AM -0400, Shawn O. Pearce wrote:
> 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.

> 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

> 
> -- 
> Shawn.

  reply	other threads:[~2007-05-01 15:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 10:21 svn:externals using git submodules Andy Parkins
2007-05-01 15:07 ` Chris Shoemaker
2007-05-01 15:22   ` Shawn O. Pearce
2007-05-01 15:36     ` Chris Shoemaker [this message]
2007-05-01 15:40       ` Shawn O. Pearce
2007-05-01 18:36       ` Andy Parkins
2007-05-01 18:39         ` Andy Parkins
2007-05-01 19:17         ` Chris Shoemaker
2007-05-01 19:48           ` Andy Parkins
2007-05-01 20:23             ` Chris Shoemaker
2007-05-01 22:19               ` Linus Torvalds
2007-05-01 22:37                 ` Junio C Hamano
2007-05-01 23:16                   ` Shawn O. Pearce
2010-01-20 13:58 ` Michel Jouvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070501153626.GA21182@pe.Belkin \
    --to=c.shoemaker@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).