Re: git-svn tags and branches

[David Kastrup <dak@gnu.org>]

Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:

> I've recently started using git and I like it so much that
> I've decided to start using it also for some svn-based
> projects (in particular, rbot http://linuxbrit.co.uk/rbot).
>
> The long term goal would be to move the project to git, but
> for the time being (among the other things we're waiting for
> Trac to have proper support for git, which is something that
> won't happen before Trac 0.12 at least) I've decided to
> experiment with a dual git/svn development process, using
> (of course) git-svn.
>
> My experience with toying around with it for a couple of
> hours has been extremely positive, but I've got some
> questions, especially about the tags and branch management.
>
> Currently, git-svn imports svn tags as lightweight git tags.

It does?  I see them as branches.

> I was susprised when I discovered this (from 'git describe'
> failing and some helpful assistance on the IRC channel), so
> I'm now wondering: is there a technical reason why they
> aren't converted to annotated tags? If not, would it be
> possible to implement this in git-svn, possibly with some
> way to 'fix' existing git-svn repository?

I actually don't see how one can safely make them tags at all (rather
than branches) since Subversion does not enforce the members of a
"tags" subdirectory to remain unchanged after the initial copy.
Basically, tags are not different from branches in Subversion from
what you can do with them.

> My second question concerns the uses of branche in git-svn,
> but it might come from a not perfect understanding of the
> branching mechanism in git (and yes, I've read the
> documentation and Wiki pages).

I'll leave that question to people who actually understand git-svn and
git branches.

-- 
David Kastrup