Conference smurf::buildhelp

976.0. "accessing revisions from retired backingtrees (re: disks)" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Wed Oct 05 1994 12:11

Date Of Receipt: 	 5-OCT-1994 10:46:01.58
From: 	FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	adams@DEC:.zko.flambe
CC: 	metsch odehelp useg
Subj: 	accessing revisions from retired backingtrees (re: disks)
> To: 	[email protected]
> Subject: 	disks
> Date: 	Tue, 04 Oct 94 15:33:45 -0400
> From: 	[email protected]
> X-Mts: 	smtp

> 
> Hi Josh
> 
> I have a 2.0 cld of a problem that is fixed in 3.0 and am having
> a terrible time locating the submit that fixed the problem.
> 
> I've mounted goldos.bl10 and found that it is fixed for that.
> However, I need it to be narrowed down much more.  There is only
> a disk for bl2 and bl3.... nothing from 4 to 9.  Do they exist
> somewhere?
> 
> Also, why can't I mount bl2 and bl3?
> 
> Stephanie Adams


Stephanie, we only save the last 2-3 baselevels/prebaselevels for
any stream, and when it's done, the last baselevel only is saved.
The bl2 and 3 you see are just old links that should have been rm'd.

ODE has history information, however, from the beginning of time,
for every file.  If you know the file(s) you're interested in,
and you know the fix went into gold, do this:

	blog -rGOLDOS filename(s)

this will show you a full history of all the versions submitted
into gold.  You can then check out any of these revisions (unlocked,
i.e. read-only) as follows:

	bco -rGOLDOS_BL5 file    
or	bco -r1.1.5.3 file      (a made-up number)

The symbols like GOLDOS_BL5 correspond to specific versions; the header
part of blog shows you this.     

If you see in the history a particular delta that has the exact
fix you want, you can pull out and merge this diff as follows:

	bco -j1.1.5.2:1.1.5.3 file     (again made-up numbers)

If you want to talk with me more on this you can give me a 
ring at 1-1548.

	-josh