Hi Dan

   I suggest the following:

1- You export the code from NOF SourceForge repository - or the mirror
pointed to by Robert - into a local dir on your machine.
2- Then you import this exported code into location(s) you want in
Isis repository.

I've never seen a way in any SCM tool using which you can move code
around to different repositories while keeping history, and maybe they
deal with this case as if you are adding the code into the new
repository as being new code.

svnadmin, as I said needs direct access to the path of the repository
on HDD, it is for administering the repo.

On Wed, Sep 29, 2010 at 6:39 PM, Robert Matthews
<[email protected]> wrote:
> I have a mirror that I will/can do an svn export from (once I've run all the
> conversion scripts that I am preparing).
>
> Rob
>
> On 29/09/10 19:16, Mohammad Nour El-Din wrote:
>>
>> I checked about the svnadmin dump, but it works on paths not URL(s),
>> do you have access to the file system where NOF SVN repository is
>> located ?
>>
>> On Wed, Sep 29, 2010 at 5:33 PM, Dan Haywood<[email protected]>  wrote:
>>
>>>
>>>  On 28/09/2010 10:43, Mark Struberg wrote:
>>>
>>>>
>>>> Next steps:
>>>>
>>>> Dan, could you please create a
>>>>
>>>> /private/initial-import/[subprojects]
>>>>
>>>
>>> I've now done this:
>>> /private/initial-import/nakedobjects ... for the NOF
>>> /private/initial-import/starobjects/xxx ... for each of my sister
>>> projects.
>>>
>>>
>>>>
>>>> and import the old SVN history of those projects?
>>>>
>>>
>>> Should it be svn import (which won't maintain history) or svnadmin load
>>> (which, I think, does)?    I got the impression that it should be the
>>> latter?
>>>
>>> Thanks
>>> Dan
>>>
>>>
>>
>>
>>
>
>



-- 
Thanks
- Mohammad Nour
  Author of (WebSphere Application Server Community Edition 2.0 User Guide)
  http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

"Stay hungry, stay foolish."
- Steve Jobs

Reply via email to