From: Eric Wong <normalperson@yhbt.net>
To: Sam Vilain <sam@vilain.net>
Cc: Mike Frysinger <vapier.adi@gmail.com>, git@vger.kernel.org
Subject: Re: git-svn: pulling from local mirror but committing via svn+ssh
Date: Fri, 21 Dec 2007 20:35:28 -0800 [thread overview]
Message-ID: <20071222043528.GB18812@soma> (raw)
In-Reply-To: <8bd0f97a0712200821j778c12a9g9d42bf02482d953c@mail.gmail.com>
Mike Frysinger <vapier.adi@gmail.com> wrote:
> i have local (fast) mirrors of the svn trees i use, so i normally keep
> everything pointing at those. when i need to commit, i use `svn
> switch --relocate ...` to flip to the svn+ssh master, and then flop
> back to the local mirror. it actually works out nicely.
>
> my reading of git-svn(1) seems to indicate that git-svn cant really
> handle switching of repository URLs on the fly ?
> http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
>
> i tried tweaking my .git/config and changing the url to my svn+ssh,
> but it seems any modification in the URL just causes errors ...
> vapier@G5[ppc] git $ git-svn dcommit
> Use of uninitialized value in concatenation (.) or string at
> /usr/bin/git-svn line 384.
> Committing to ...
> Unable to determine upstream SVN information from HEAD history
>
> guess i'll have to bite the bullet and just clone the svn+ssh repo :/
>
> (i'm using 1.5.3.7 over here)
Sam:
Can useSvmProps handle this? I honestly forgot how that stuff
was supposed to work with SVK/svn-mirror.
Mike:
On the other hand, there's little point in keeping local mirrors around
when using git-svn since git already does that for you :)
--
Eric Wong
next prev parent reply other threads:[~2007-12-22 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 16:21 git-svn: pulling from local mirror but committing via svn+ssh Mike Frysinger
2007-12-22 4:35 ` Eric Wong [this message]
2007-12-22 9:16 ` Sam Vilain
2007-12-22 9:32 ` Mike Frysinger
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=20071222043528.GB18812@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
--cc=vapier.adi@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.