[p4] Getting file change information for a change

[Robert Cowham]

Another alternative:

P4 files @xxx, at xxx

Or

P4 files @xxx,xxx

Same results 

Revision ranges are powerful things! Ranges can start or end with any of
revisions, changelists, labels, dates etc.

Same syntax works for other commands such as p4 changes

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Raja Aluri
> Sent: 09 November 2007 22:43
> To: Gross, Steve; perforce-user at perforce.com
> Subject: Re: [p4] Getting file change information for a change
> 
> Is this what you wanted?
> 
> p4 files @=xxx
> 
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Gross, Steve
> Sent: Friday, November 09, 2007 12:35 PM
> To: perforce-user at perforce.com
> Subject: [p4] Getting file change information for a change
> 
> Pursuant to my earlier discussion:
> 
> I want to know what files are affected by a particular 
> submitted change.
> For change X, for instance, I want a list of files affected.
> 
> I've found that I can execute the following command:
>   p4 files //... at xxx
> 
> Where 'xxx' is the change number, and I get a fair amount of 
> information. If I pipe it through grep:
>   p4 files //... at xxx | grep xxx
> 
> Then I get exactly what I need--a list of files affected 
> specifically in change xxx.
> 
> Is there a way I can get p4 to give me the grepped info 
> directly, rather than fetching it all and THEN piping it 
> through grep? It would save a lot of time.
> 
> Thanks,
> --Steve
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>