From: Stephen Bash <bash@genarts.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [PATCH 2/4] Allow reading svn dumps from files via file:// urls.
Date: Wed, 11 Jul 2012 13:49:46 -0400 (EDT) [thread overview]
Message-ID: <33a7c123-9db7-4f27-960b-d13db9a71f97@mail> (raw)
In-Reply-To: <7vbojmfd1u.fsf@alter.siamese.dyndns.org>
----- Original Message -----
> From: "Junio C Hamano" <gitster@pobox.com>
> To: "Dmitry Ivankov" <divanorama@gmail.com>
> Cc: git@vger.kernel.org
> Sent: Wednesday, July 11, 2012 1:00:29 PM
> Subject: Re: [PATCH 2/4] Allow reading svn dumps from files via file:// urls.
>
> Dmitry Ivankov <divanorama@gmail.com> writes:
>
> > Florian Achleitner <florian.achleitner.2.6.31 <at> gmail.com>
> > writes:
> >
> > > Especially for testing and development it's useful to bypass
> > > svnrdump and replay the svndump from a file without connecting to
> > > an svn server.
> > >
> > > Add support for file:// urls in the remote url. e.g.
> > > svn::file:///path/to/dump When the remote helper finds an url
> > > starting with file:// it tries to open that file instead of
> > > invoking svnrdump.
> >
> > file:// is a bad choice because file:// style repo urls are valid
> > for svn and it's for local repos rather than dumpfiles.
>
> Thanks; I had the same reaction when I saw it.
>
> > Maybe something like dumpfile:// instead?
>
> If dumpfile:// pseudo URL is an established convention in the
> Subversion land, that sounds like a sensible direction, but if that is
> not the case, it may be cleaner if you can find some other way to
> convey the information to the backend out-of-band, instead of
> overloading it in the URL used to access the repository.
Others may have a different opinion, but in my experience dump files are always handled via stdin/stdout in Subversion land. For example:
http://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.c.dump.html
http://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.c.load.html
http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.filtering
I'm not sure that helps in this scenario, but that was the convention I grew used to.
Stephen
next prev parent reply other threads:[~2012-07-11 17:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 13:38 [RFC/PATCH 0/4] GSOC remote-svn Florian Achleitner
2012-07-11 13:38 ` [PATCH 1/4] vcs-svn: add fast_export_note to create notes Florian Achleitner
2012-07-11 13:38 ` [PATCH 2/4] Allow reading svn dumps from files via file:// urls Florian Achleitner
2012-07-11 13:38 ` [PATCH 3/4] Create a note for every imported commit containing svn metadata Florian Achleitner
2012-07-11 13:38 ` [PATCH 4/4] When debug==1, start fast-import with "--stats" instead of "--quiet" Florian Achleitner
2012-07-11 14:29 ` [PATCH 2/4] Allow reading svn dumps from files via file:// urls Dmitry Ivankov
2012-07-11 17:00 ` Junio C Hamano
2012-07-11 17:49 ` Stephen Bash [this message]
2012-07-15 14:26 ` [PATCH] Fix overwritten remote ref on with fast-import Florian Achleitner
2012-07-16 0:30 ` Jonathan Nieder
2012-07-16 4:33 ` Junio C Hamano
2012-07-16 22:33 ` Florian Achleitner
2012-07-17 3:27 ` Jonathan Nieder
2012-07-17 9:54 ` Florian Achleitner
2012-07-17 13:48 ` Jonathan Nieder
2012-07-17 20:52 ` Florian Achleitner
2012-07-17 21:02 ` Jonathan Nieder
2012-07-17 22:25 ` Florian Achleitner
2012-07-17 9:56 ` [PATCH] Add explanatory comment for transport-helpers refs mapping Florian Achleitner
2012-07-17 16:04 ` Jonathan Nieder
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=33a7c123-9db7-4f27-960b-d13db9a71f97@mail \
--to=bash@genarts.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).