On Oct 7, 2008, at 17:54, Looking through a Glass Onion. wrote:
> Thanks for your reply and recommendations. I'll double check on the
> "advertised" limitation of svk with regard to svn:externals, and
> also see
> about route between git and scm.
>
> You probably haven't gotten to it yet, but I sent a follow-up to this
> earlier today (which did NOT contain these suggestions, so again
> thank you
> for them) -- I'm investigating using cygwin as a wrapper-that-
> supports-
> link for the Windows build environment -- links seem like what we want
> anyway, and the Windows build tools can, of course, be called from
> there.
>
> IFF, after all is said and done (and also working), I took the time
> to add
> --ignore-externals to `svn import ...` -- which is where, to my
> untrained
> svn eye it (also) belongs, do you think it would be useful, and fit
> with
> the svn mantra, or is there a better way to cover this space, and
> whatever
> related version-control spaces yet to be covered? There doesn't
> *seem*
> like there's enough time in my schedule for this, but IFF...
It's a bit peculiar to have an "--ignore-externals" option in "svn
import" since the purpose of "svn import" is to import an unversioned
directory into a repository. So that option would only apply if
you're importing from an existing working copy into a different
repository, which is an unusual use of "svn import", though it does
know about this use and does already know to ignore the .svn
directories.
---------------------------------------------------------------------
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-08 01:04:58 CEST