[p4] Has change propagated ?
robert at vizim.com
Wed Mar 11 06:08:12 PDT 2009
Ah - if you don't know the target then integ -n isn't much use.
For performance reasons I would run things like integrated/filelog/changes
on a path with a wildcard and do local processing rather than looping on a
10,00 file changelist and doing 10,000 individual p4 commands...
> -----Original Message-----
> From: G Barthelemy [mailto:gb.perforce at googlemail.com]
> Sent: 11 March 2009 11:40
> To: Robert Cowham
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Has change propagated ?
> On Wed, Mar 11, 2009 at 11:30 AM, Robert Cowham
> <robert at vizim.com> wrote:
> > Don't forget "p4 integ -n" to show you what integrations Perforce
> > thinks need to be done.
> > Thus:
> > p4 integ -n source/... at 1456 target/...
> > p4 integ -n source/... at 1456, at 1456 target/...
> Yes but doesn't that suppose target/... to be known ? In my
> case, it isn't. I want to know if any revision in 1456 has
> been integrated to anywhere. Therefore, "anywhere" would most
> likely always be a candidate to p4 integ.
More information about the perforce-user