# Perforce Public Depot Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#  Status:        Job status; [open/closed/suspended].  Required
#  Project:       The project this job is for [none/cdsp4/jam/p4hl]  Optional.
#  Severity:      [A/B/C] (A is highest)  Required.
#  ReportedBy     The user who created the job. Can be changed.
#  ReportedDate:  The date the job was created.  Automatic.
#  ModifiedBy:    The user who last modified this job. Automatic.
#  ModifiedDate:  The date this job was last modified. Automatic.
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#  Description:   Description of the job.  Required.
#  DevNotes:      Developer's comments.  Optional.

Job:	job000002

Status:	closed

Project:	p4hl

ReportedBy:	sam_stafford

ReportedDate:	2001/10/18 01:42:31

ModifiedBy:	shawn_hladky

ModifiedDate:	2008/04/13 13:00:54

Description:
	Irrelevant revisions are left lying around - they shouldn't appear at all.
	
	To reproduce: set up an integration relationship such that some revisions 
	are not relevant (such as descendants of a file that was branched once).  
	The irrelevant revisions will show up piled on top of each other at the 
	"earliest" position.

DevNotes:
	The fact that the irrelevant revs aren't moving to the correct temporal 
	position indicates that the underlying FileLogCache routines are 
	functioning correctly.  Probably a matter of CObjectFile::Expand() not 
	filtering for relevant revisions (those with either tocheck or
	fromcheck true).