Re: git-svn and svn:externals, was Re: Hackontest ideas?

From: Avery Pennarun <apenwarr@gmail.com>
Date: Jul 29, 2008, 16:08 UTC
Message-ID: <32541b130807290908l13e753d8t1357db452a04f491@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0807291502450.4631@eeepc-johanness>

On 7/29/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

Show 11 quoted lines

>  On Tue, 29 Jul 2008, Jakub Narebski wrote:
>  > If I understand correctly with version 1.5 svn:externals can be
>  > specified using "peg revisions", so they could refer to some specific
>  > revision of 'external', like git submodules.
>
> ... which only means that if they had done that from the beginning, it
>  the git-svn enhancement would be easy.
>
>  But as they did not have it from the beginning, anybody tackling git-svn
>  and svn:externals will have to come up with sensible semantics for the
>  hard case.

One option would be to simply attach the submodule to the "latest commit of the svn:external at the time the supermodule svn commit was made". Basically, enforce git-submodule's precise revision feature retroactively onto svn:externals.

I think this would be perfectly fine in my own projects, for example: it's what I wanted in the first place, but svn didn't have this feature, so I faked it by branching/tagging the external repo whenever I wanted to link to a particular revision.

Have fun,

Avery