All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-svn tags and branches
Date: Mon, 27 Aug 2007 19:08:47 +0200	[thread overview]
Message-ID: <fav0e9$bbh$1@sea.gmane.org> (raw)
In-Reply-To: A0329662-9C87-44C2-84E4-4F60DCC1E95F@lrde.epita.fr

On Monday 27 August 2007 17:36, Benoit SIGOURE wrote:

> On Aug 27, 2007, at 5:31 PM, Mike Hommey wrote:
> 
>> On Mon, Aug 27, 2007 at 05:09:30PM +0200, David Kastrup  
>> <dak@gnu.org> wrote:
>>> 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.
>>
>> Well, git-svn could make tags when the tag/branch is created in  
>> subversion,
>> and then create a branch on the first commit on top of that tag/ 
>> branch in
>> svn.
> 
> Or update the tag ref in Git so that it points to the new "HEAD" of  
> the SVN tag.But all in all, it's more consistent to have it look  
> like a branch from the Git point of view, because that's really what  
> it is after all.

Yes and no. By making it just a branch you lose the tag POV on that
particular commit, and this is, in a way, a loss of information: yes, it
can behave like a branch but most projects use it as a tag.

I think the best approach is to have an annotated tag 'tagname'
corresponding to the tags/tagname copy on the svn side in addition
to the 'tags/tagname' branch that is currently used to track its head.

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2007-08-27 17:09 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 [this message]
2007-08-27 15:42   ` Giuseppe Bilotta
     [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='fav0e9$bbh$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.