git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: H Krishnan <hetchkay@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: svn repository URL and git
Date: Thu, 28 Oct 2010 21:02:27 +0200	[thread overview]
Message-ID: <20101028190227.GC46314@acme.spoerlein.net> (raw)
In-Reply-To: <loom.20101028T184823-831@post.gmane.org>

On Thu, 28.10.2010 at 16:58:28 +0000, H Krishnan wrote:
> 
> Hi,
> I think I resolved this problem by using --rewrite-root as suggested. I used a 
> dummy root during the git-svn clone:
> 
> git-svn clone --rewrite-root http://git.is.great <myrepo>
> 
> All my commit messages now have http://git.is.great but I am able to change the 
> repository URL and continue.
> 
> Could this approach be used as an insurance against svn url changes? When 
> initializing the repository, we could use --rewrite-root. Subsequently, if the 
> svn repository relocates, we need to edit only .git/config. 

Yes, that's exactly what the rewrite-url was introduced for, you can
even clone from a local svnsync mirror (iff the UUID matches, you have
to setup the mirror in a special way ...).

So, every developer must use:

$ git svn clone --rewrite-root CANONICAL-URL-NEVER-TO-CHANGE <whatever-url-is-convenient>

Oh, and all devs must use the same authormap (or no authormap at all).

hth,
Uli

  reply	other threads:[~2010-10-28 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 15:05 svn repository URL and git H Krishnan
2010-10-27 15:31 ` Mathias Lafeldt
2010-10-27 16:15   ` H Krishnan
2010-10-28 16:58     ` H Krishnan
2010-10-28 19:02       ` Ulrich Spörlein [this message]
2010-10-28 19:31         ` Mathias Lafeldt
2010-10-28 19:37           ` Ulrich Spörlein
2010-10-29  3:07           ` H Krishnan

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=20101028190227.GC46314@acme.spoerlein.net \
    --to=uqs@spoerlein.net \
    --cc=git@vger.kernel.org \
    --cc=hetchkay@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 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).