All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Sébastien Mazy" <melyadon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to prefix existing svn remotes?
Date: Fri, 23 Jan 2009 14:02:31 +0100	[thread overview]
Message-ID: <4979BFE7.8090402@drmicha.warpmail.net> (raw)
In-Reply-To: <20090123124231.GA17616@locahost>

Sébastien Mazy venit, vidit, dixit 23.01.2009 13:42:
> Hi Michael,
> 
> Thanks for your reply.
> 
> On Fri, Jan 23, 2009 at 12:13:18PM +0100, Michael J Gruber wrote:
>> The following works for me:
>>
>> 0) fetch to make sure you're current (optional)
>> 1) edit .git/config and add the prefix (right hand side of the
>> refpsecs), or really rename in any way you want
> 
> OK.
> 
>> 2) rename the existing remote branches in the same way
> 
> I'm not sure how I can do it. 'trunk' is the only remote-tracking svn
> branches under .git/refs/. Here is how it looks:
> 
> ls -R .git/refs
>  .git/refs:  heads  remotes  tags
>  .git/refs/heads:  master
>  .git/refs/remotes:  trunk
> 
> Still, a 'branch0' remote exist:
> 
> git show-ref
>  refs/heads/master
>  refs/remotes/branch0
>  refs/remotes/trunk

You can do (bash)

for b in trunk branch0
do
  git update-ref refs/remotes/yournewprefix/$b refs/remotes/$b
  git update-ref -d refs/remotes/$b
done

OTOH, any incarnation of "git -m" (with or without "-r", specifying
refs/remotes/trunk, remotes/trunk or trunk) failed.

Michael

  reply	other threads:[~2009-01-23 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 17:32 How to prefix existing svn remotes? Sébastien Mazy
2009-01-23 11:13 ` Michael J Gruber
2009-01-23 12:42   ` Sébastien Mazy
2009-01-23 13:02     ` Michael J Gruber [this message]
2009-01-23 17:13       ` Sébastien Mazy
2009-01-23 17:51         ` Jakub Narebski

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=4979BFE7.8090402@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=melyadon@gmail.com \
    /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.