git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to prefix existing svn remotes?

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jan 23, 2009, 13:02 UTC
Message-ID
<4979BFE7.8090402@drmicha.warpmail.net>
In-Reply-To
<20090123124231.GA17616@locahost>
Sébastien Mazy venit, vidit, dixit 23.01.2009 13:42:
Show 29 quoted lines
> 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
Previous: Sébastien MazyNext: Sébastien Mazy
Message 4 of 6 in “How to prefix existing svn remotes?”
  1. Sébastien MazyJan 22, 2009
  2. Michael J GruberJan 23, 2009
  3. Sébastien MazyJan 23, 2009
  4. Michael J GruberJan 23, 2009
  5. Sébastien MazyJan 23, 2009
  6. Jakub NarebskiJan 23, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.