From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-svn tags and branches
Date: Mon, 27 Aug 2007 17:42:36 +0200 [thread overview]
Message-ID: <faurcl$p0o$1@sea.gmane.org> (raw)
In-Reply-To: 867inhqaj9.fsf@lola.quinscape.zz
On Monday 27 August 2007 17:09, David Kastrup wrote:
> Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
>>
>> Currently, git-svn imports svn tags as lightweight git tags.
>
> It does? I see them as branches.
Oh, I thought that them being in refs/remote/tags meant they
were remote tags. But yes, I had noticed them appearing with
git branch -r
>> 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.
Although this is technically true, I doubt there are many Subversion
projects which alter the members of a tags subdirectory. So the fact
that it's technically possible doesn't really mean it happens.
I mean, even in git you can do some pretty dirty tag stuff. It may
not be as straightforward as in svn, but still ...
So yes, I still think that an option to convert svn tags to annotated
tags would be appropriate. Wether or not it should be default, it's
a different matter, of course.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2007-08-27 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 14:08 git-svn tags and branches Giuseppe Bilotta
2007-08-27 15:09 ` David Kastrup
2007-08-27 15:31 ` Mike Hommey
2007-08-27 15:36 ` Benoit SIGOURE
2007-08-27 17:08 ` Giuseppe Bilotta
2007-08-27 15:42 ` Giuseppe Bilotta [this message]
[not found] ` <46D38B3D.6070809@vilain.net>
[not found] ` <85absc6we7.fsf@lola.goethe.zz>
[not found] ` <cb7bb73a0708280209r36136128x7bce310bf4fd4f66@mail.gmail.com>
[not found] ` <86sl64nhc1.fsf@lola.quinscape.zz>
[not found] ` <cb7bb73a0708280237v6f248517h183174bc41296df3@mail.gmail.com>
[not found] ` <46D4A664.4070007@vilain.net>
[not found] ` <cb7bb73a0708281620v41383ed8w728af0112d2a6360@mail.gmail.com>
[not found] ` <46D4ECE2.9020806@vilain.net>
2007-08-29 8:41 ` Giuseppe Bilotta
2007-08-29 8:56 ` Andreas Ericsson
2007-08-29 8:59 ` Junio C Hamano
2007-08-29 10:53 ` Giuseppe Bilotta
2007-08-29 20:15 ` Junio C Hamano
2007-08-29 21:06 ` Giuseppe Bilotta
[not found] ` <cb7bb73a0708291402r3e9dfdeeh85bcc47ef9eba782@mail.gmail.com>
[not found] ` <7vy7fu9h9n.fsf@gitster.siamese.dyndns.org>
2007-08-29 21:27 ` Giuseppe Bilotta
2007-08-30 10:21 ` Eric Wong
2007-08-30 11:44 ` Giuseppe Bilotta
2007-08-30 12:25 ` Peter Baumann
2007-08-30 16:01 ` Giuseppe Bilotta
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='faurcl$p0o$1@sea.gmane.org' \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.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).