[p4] will the real change revision please step forward

jab jab at pobox.com
Tue Mar 22 17:08:47 PST 2005


On Mar 22, 2005, at 3:02 PM, John-Mason P. Shackelford wrote:

> 1. Keep an MD5 of each revision. (Doesn't this already happen?) Use 
> assign a letter code 'aaa', 'aab', etc. for each unique hash in all of 
> the related revisions being displayed in the revision graph or 
> revision history. Display this identification where every revision is 
> shown so that we can easily see the lineage of a revision which has 
> just been copied from branch to branch. Allow filtering (out or in) of 
> revisions bearing the same fingerprint so as to allow us to quickly 
> answer the question "on what branch was this revision of the file 
> introduced?"

	Does this strategy  rely on the changes being accepted wholesale from 
the branch, with no 'merge into' operation?   That might be 
unrealistic.

	-Jeff Bowles




More information about the perforce-user mailing list