Bug 77526

Summary:	RCS-Tag corrupted by Perforce
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Need Real Name <hschroeder>
Component:	documentation	Assignee:	ccm-bugs-list
Status:	CLOSED WONTFIX	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://ccm.redhat.com/resources/perforce/cvs-perforce-transition.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-08-22 12:55:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2002-11-08 15:57:57 UTC

Description of Problem:
the Webpage "CVS to Perforce Transition Guide" at 
http://ccm.redhat.com/resources/perforce/cvs-perforce-transition.html
contains a comparison of RCS-Tags in CVS and Perforce. This Page contains
lots of $Id: ... Tags which got corrupted by the Perforce Server (Search
for $Id), as it updates them. This Page should not be checked in as text+k
but as pure text or the Tags shoulb be reformated like $_Id: ... with the
appropriate notion.

Version-Release number of selected component (if applicable):
$Id: //websites/ccm/resources/perforce/cvs-perforce-transition.html#1


How Reproducible:
Open page in Webbrowser and search for $Id

Actual Results:
The CVS reportetd tag is the same as the one from Perforce. Both are not the 
original ones as they are created by Perforce Server.

Expected Results:
Difference like
 CVS: $Id: Page0000161.scp,v 1.1 2002/11/07 16:48:15 HSchroeder Exp $
 Perforce: $Id: //depot/Page0000161.scp#2 $ 

Additional Information:
All RCS-Tags are corrupted, not only the $Id ... ones.
It is necessary to get the original source of this Webpage as it is modified in 
the repository.

Comment 1 Richard Li 2003-08-22 12:55:09 UTC

we're not maintaining this guide any more since we migrated to p4 a long time
ago ;-)