23 messages in com.perforce.revml[revml] Re: [p4] cvs to perforce usin...
FromSent OnAttachments
barries02 Jul 2001 08:36 
david d zuhn03 Jul 2001 08:48 
barries03 Jul 2001 09:38 
david d zuhn03 Jul 2001 11:43 
barries03 Jul 2001 13:22 
barries03 Jul 2001 21:56 
david d zuhn05 Jul 2001 09:13 
barries05 Jul 2001 10:58 
david d zuhn05 Jul 2001 11:17 
barries05 Jul 2001 11:25 
david d zuhn05 Jul 2001 11:44 
barries05 Jul 2001 12:20 
barries16 Jul 2001 11:51 
david d zuhn16 Jul 2001 11:51 
david d zuhn18 Jul 2001 12:04 
barries18 Jul 2001 12:40 
david d zuhn18 Jul 2001 12:56 
barries18 Jul 2001 14:09 
ste...@vance.com19 Jul 2001 07:37 
barries19 Jul 2001 07:42 
david d zuhn19 Jul 2001 11:19 
barries19 Jul 2001 11:25 
barries19 Jul 2001 13:54 
Subject:[revml] Re: [p4] cvs to perforce using VCP package......
From:david d zuhn (zo@bravara.com)
Date:07/05/2001 11:44:29 AM
List:com.perforce.revml

At 02:25 PM 7/5/2001 -0400, barries wrote:

On Thu, Jul 05, 2001 at 01:17:42PM -0500, david d zuhn wrote:

It looks like you want to copy /kernel/sys/... in cvs to //depot/bravos/... in perforce, but it looks like vcp is trying to put it in to //depot/bravos/sys/...,

I in effect would like to move the directory sys from cvs:/kernel to p4://depot/bravos/, keeping everything in the sys/ directory exactly the same.

Ok, so you'd end up with //depot/bravos/sys containing everything that /kernel/sys contained. Looks like that's what vcp's trying to do, but the command line

vcp cvs:/kernel/sys/... p4://depot/bravos

*should* copy the contents of the /kernel/sys "directory" to the //depot/bravos "directory".

Well, that's certainly not what happens. With the patch you just sent, the procedure I sent before worked exactly as I hoped it would, with the entire contents of /kernel/sys now properly located in p4://depot/bravos/sys

If that's not the intent of the VCP system, and that I should really have to specify p4://depot/bravos/sys as the destination (and I can see that would probably be the best choice for syntax), then there's still a file root naming bug in place.