[p4] Tracking a bug through its integration history?

[steve@vance.com]

Yeah, the command line is great for tracking it backwards, but limited in 
tracking it forward. If I wanted to track it forward, I would probably use 
the P4V Revision Graph starting with that revision. 

Steve 

Roy Smith writes: 

> In change 60384 (about a year ago), we introduced a bug.  In this  
> particular case, the bogus code was confined to a single source file,  
> but in the general case, it might not be. 
> 
> How do I find all the places this change has been propagated to via  
> integrations into various branches?  I know I can do "p4 filelog",  
> but that just gets the 1st generation of integrations.  It doesn't  
> recursively track all the places the change was integrated into after  
> that. 
> 
> -------------------
> Roy Smith <smith_roy at emc.com>
> Software Guy, EMC Common Management Group
> 44 South Broadway, 7th floor
> White Plains, NY 10601
> (914) 580-3427
> AIM: roysmith649 
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
 


Stephen Vance