On Oct 6, 2008, at 18:32, Looking through a Glass Onion. wrote:
> I've checked through the archives of this alias, and I've seen a
> few queries regarding setting up local (a.k.a. 'child')
> repositories of other repositories so version control can be done w/
> o network connectivity, then committed 'en masse' to the main
> repository at convenient times. The recommendation for this was to
> use SVK at http://svk.bestpractical.com/ -- but they don't support
> externals (at least not as of today's visit to http://
> svk.bestpractical.com/view/SVKForSubversion -- but I am
> investigating the 'proposal' and 'workaround').
svk is the tool I have most often seen recommended for this scenario.
I was not aware svk had problems with externals. You'll have to
address that with the developers of svk.
I believe there is also a gateway between git and svn that can be
used. You would use git locally, then you eventually send your git
changes up to the Subversion repository. I do not know more about it
than that. I believe this is the tool:
http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
[snip]
> Option 2 (again, to the meat of a meaninful question): Is
> there some way to get svn to ignore these externals during the
> import as it does the '.svn' folders and even better, to also
> ignore these during the export, too!)? If so, this seems like a
> much better solution as it's all internal to svn, and requires no
> special handling time or risks to folders and code.
You can ignore externals during export using "svn export --ignore-
externals". See "svn help export".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-07 23:39:44 CEST