git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Baumann <waste.manager@gmx.de>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Eric Wong <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: git-svn tags and branches
Date: Thu, 30 Aug 2007 14:25:14 +0200	[thread overview]
Message-ID: <20070830122514.GF5050@xp.machine.xx> (raw)
In-Reply-To: <cb7bb73a0708300444q73e12d72o665a8266c2a90f61@mail.gmail.com>

On Thu, Aug 30, 2007 at 01:44:35PM +0200, Giuseppe Bilotta wrote:
> On 8/30/07, Eric Wong <normalperson@yhbt.net> wrote:
> > As noted by other repliers, SVN tags can be moving targets just like
> > branches, and are treated as such by git-svn.
> >
> > I should note that tags in git can actually be updated like a branch
> > just the same way, too, it's just not as easy to "accidentally" do.
> >
> > So I'll add the ability to modify refs under the refs/tags/ namespace to
> > my git-svn TODO list (which is getting rather large).  I also plan to
> > support branches outside of the refs/remotes/ namespace so it's easier
> > to use (clone, browse from gitweb) from bare repositories.
> 
> Thank you very much, that would be very appreciated.
> 
> While we're at it: could you consider putting the svn-imported refs
> not directly under remote? something like refs/remote/svn would be
> rather cleaner.
> 

Did you have a look at the --prefix option mentioned in the manpage? I
think it does what you want.

-Peter

  reply	other threads:[~2007-08-30 12:25 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
     [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 [this message]
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=20070830122514.GF5050@xp.machine.xx \
    --to=waste.manager@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=normalperson@yhbt.net \
    /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).