Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 77526 - RCS-Tag corrupted by Perforce
RCS-Tag corrupted by Perforce
Product: Red Hat Web Application Framework
Classification: Retired
Component: documentation (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
Depends On:
  Show dependency treegraph
Reported: 2002-11-08 10:57 EST by Need Real Name
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-22 08:55:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-11-08 10:57:57 EST
Description of Problem:
the Webpage "CVS to Perforce Transition Guide" at 
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 08:55:09 EDT
we're not maintaining this guide any more since we migrated to p4 a long time
ago ;-)

Note You need to log in before you can comment on or make changes to this bug.