Yeah, we should be able to move things around once it's imported. I
imagine that it would initially get tagged as "import" with work
continuing on in trunk.
Regards,
Alan
On Jul 25, 2008, at 12:09 PM, Les Hazlewood wrote:
Actually I don't think that is possible - the existing repo already
has
'trunk', 'branches' and 'tags' that need to be preserved in the same
location.
To achieve what you're talking about, I was hoping we could just
create an
'import' branch immediately after the migration and then start using
the
trunk after that point as desired.
Would that be acceptable?
On Fri, Jul 25, 2008 at 2:49 PM, Craig L Russell <[EMAIL PROTECTED]
>wrote:
Is it too late to suggest that the top level directory for the
imported
code be "import" and not "trunk"? Using the import directory would
allow
development to continue (in import) and put all of the future Apache
deliverables into trunk.
Craig
On Jul 25, 2008, at 8:43 AM, Les Hazlewood wrote:
Ok, I'll let the infrastructure folks know they can blast away the
existing
one when performing the load.
Thanks,
Les
On Fri, Jul 25, 2008 at 11:04 AM, Alan D. Cabrera <[EMAIL PROTECTED]
wrote:
Crickey, you may be right. It's simple enough to recreate those few
files.
Regards,
ALan
On Jul 25, 2008, at 7:58 AM, Les Hazlewood wrote:
I want to do it today or tomorrow. Sunday at the latest for sure.
Just out of curiosity - I see the new SVN is being used. Won't
that
cause
a
conflict for an svnadmin load of the migrated repo? I mean,
I've never
done
an svnadmin load on anything other than a fresh repository -
anyone know
if
this is possible?
On Fri, Jul 25, 2008 at 10:49 AM, Alan D. Cabrera <[EMAIL PROTECTED]
wrote:
Les, have you been able to make your SVN dump yet? When can we
expect
this?
Regards,
Alan
Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/
jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
