> As soon as you do this, your working copy points to a directory where
> you don't have write access, so this won't work.
>
> What you need to do is import the contents of that directory into a
> Subversion repository where you *do* have write access. svn import can
> probably help you here.
>
> None of this is a very good idea, though, and doubly bad if you aren't
> aware of the possible consequences of what you're doing nor how to
> recover if something goes wrong. Thus, I would solve this problem the
> "correct way" by getting the owners of the directory to accept your
> change.
>
> good luck,
> tyler
>
As I have sent them patches some weeks ago, and the only answer I got so
far is that they will look into up if they have time is not acceptable
in the short run.
Would it make sense to checkout the external repository (or is this the
same like import anyway?), then check it into my repository, do the
changes and commit them to my subversion repository. And if they apply
the patches, I still can remove the files from my svn server, and reset
the svn:external to theirs with the new patches.
Are there any disadvantages to this (licenses would permit this)?
Thanks again
Georg
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2410783
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-24 00:09:27 CEST