| Date Of Receipt: 3-AUG-1995 10:40:18.69
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 03-Aug-1995 1038"
To: schloss@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: Re: srequest tag query
Mike, the defect number always begins with the pool name, eg ptliteos-...
This pool is the pool into which the submit went, and therefore is the
release in which the fix (first) would appear; after this, "downstream"
releases (eg ptos) would back to a baselevel in which the fix appeared,
and the fix would be propagated (& merged if needed by a dri) into that
release.
Once you've determined the release, eg ptliteos, cd to that release's
/usr/sde/osf1/build/<release>/logs directory, or, in the release eng
web page for the release in question:
http://nsa.zk3.dec.com/rengweb - Current Build Logs - pool_status
open the file "bsubmit.log". In this search for the defect number; there
may be multiple entries if the submit was done in pieces. Each submit
entry will show all of the revs which were submitted. Note that future
submits to these files would have caused the rev#s to change subsequently.
-josh
> Given an srequest tag (defect id?) how do I determine what revisions
> of which files comprise the fix? How about what release it went
> (is going) out in?
>
> Mike
>
|