23 messages in com.perforce.revml[revml] Re: breaking up long command ...
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: breaking up long command lines....
From:david d zuhn (zo@bravara.com)
Date:07/18/2001 12:56:55 PM
List:com.perforce.revml

At 03:40 PM 7/18/2001 -0400, barries wrote:

On Wed, Jul 18, 2001 at 02:05:11PM -0500, david d zuhn wrote:

I'm trying another run with VCP, on a larger part of a source tree now, and running into command line length limitations.

One labelsync command is about 172k long in terms of the number of files specified (about 3200).

Holy cow! Are there a huge number of files in the label, or has something gone badly awry in VCP?

Honestly, I'm not sure I can answer that question, since I haven't looked at that aspect of VCP, and I'm not yet fully fluent in Perforce. I need some more context to be able to answer the question.

This is a tree with about 6800 files, most of which were imported at one time into CVS, and then most have not been modified since.

I'd bet that running several of the p4 commands through xargs instead of a direct invocation may neatly solve the problem.