From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Sam Vilain" <sam@vilain.net>
Cc: "Eric Wong" <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: git-svn: pulling from local mirror but committing via svn+ssh
Date: Sat, 22 Dec 2007 04:32:36 -0500 [thread overview]
Message-ID: <8bd0f97a0712220132w6fdfd7ddud96811d4af8b431f@mail.gmail.com> (raw)
In-Reply-To: <476CD5E1.9020204@vilain.net>
On Dec 22, 2007 4:16 AM, Sam Vilain <sam@vilain.net> wrote:
> Eric Wong 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.
> >
> > Can useSvmProps handle this? I honestly forgot how that stuff
> > was supposed to work with SVK/svn-mirror.
>
> It's precisely this use case. If you are syncing with SVN::Mirror, part
> of SVK, or via svnsync, these tools leave breadcrumbs as svn properties
> that point to where the repository was copied from. So, in your commit
> log the message will be the URL of the immediately[*] upstream
> repository. SVN didn't ever really support clone per se, what did you
> use to copy the repository?
we publish the raw svn tree via rsync so people can create their own svn mirrors
sounds like it's just easier to mirror the original and since this
isnt a terribly large repo (~50 meg w/out any scm stuff), that's ok
-mike
prev parent reply other threads:[~2007-12-22 9:33 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
2007-12-22 9:16 ` Sam Vilain
2007-12-22 9:32 ` Mike Frysinger [this message]
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=8bd0f97a0712220132w6fdfd7ddud96811d4af8b431f@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=sam@vilain.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).