[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

2228.0. "Possible problem with source control for kernel/io/dec/ws/pcxal.c" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon May 06 1996 15:34

Date Of Receipt: 	18-APR-1996 11:07:43.87
From: 	SMURF::KAMLIA::franzini "John Franzini MSD  18-Apr-1996 1105"
To: 	odehelp@DEC:.zko.kamlia
CC: 	franzini@DEC:.zko.kamlia
Subj: 	Possible problem with source control for kernel/io/dec/ws/pcxal.c

Hello.

I am making a change to ./kernel/io/dec/ws/pcxal.c in the support pools.

When I go into a sandbox backed to v32de1supportos and do a bco on it, I
get Revision 1.1.11.8.

However, the revision in all the submit trees and .nightly trees for both
the support pools and the development pools back to V3.0 is 1.1.11.9.

blog -r shows .8 as the current version for all these pools.

I can't even find where .9 was submitted in any of the bsubmit.log files.

The differences between .8 and .9 are minor, but it is troubling that the
source control for this module seems messed up.

Am I missing something?

Thanks,
John F.


T.RTitleUserPersonal
Name
DateLines
2228.1Re: Possible problem with source control for kernel/io/dec/ws/pcxal.cAOSG::FILTERAutomatic Posting Software - mail to flume::puckMon May 06 1996 15:3816
Date Of Receipt: 	18-APR-1996 13:59:57.29
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  18-Apr-1996 1357"
To: 	franzini@kamlia.zk3.dec.com
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: Possible problem with source control for kernel/io/dec/ws/pcxal.c

I will investigate this; thanks for pointing it out.

There have been occasional non-caught errors in our "markrcs" process;
if it's any consolation, yesterday I submitted a change in the tools we
use which will catch and flag errors and in many cases make sure they
get fixed when the next (.nightly or whatever) tree is created.

-josh


2228.2re: Possible problem with source control for kernel/io/dec/ws/pcxal.cAOSG::FILTERAutomatic Posting Software - mail to flume::puckMon May 06 1996 17:5091
Date Of Receipt: 	19-APR-1996 16:29:45.16
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  19-Apr-1996 1627"
To: 	franzini@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	re: Possible problem with source control for kernel/io/dec/ws/pcxal.c

John, look what I discovered, looking into this more deeply...

No corrective action has been taken yet in the rcs pools to correct bco's
but it will be addressed early next week...

Thanks very much for alerting us to this.     -josh


------- Forwarded Message

To: ppt
Cc: johnf, brett, releng, tresvik
Subject: Pt pools dropped LANGUAGE AND KEYBOARD HANDLING source code
Date: Fri, 19 Apr 96 16:23:43 -0400
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf>
X-Mts: smtp

PPT, I don't know how important this "lost code" is relative to
platinum, someone knowledgeable about the component should track it
down.  It at least needs to be addressed in steel.


Note: This has not yet been QAR'd, but I wanted to get it out now.
(I seem to no longer be able to login to gorge, and I couldn't
find the web page for qar submits, just viewing)


Abstract:
LANGUAGE AND KEYBOARD HANDLING SOURCE CHANGES INADVERTENTLY DROPPED

It has just been discovered that some work submitted on 5/31/94 was
inadvertently dropped from the pool as of platinum, in two files.

>From what I have been able to determine, three of the files listed in
srequest bl010/goldos-2375-jestabro, dated Apr 22 94, were resubmitted
on May 31 at 20:55GMT and at that time there was an ODE error of some sort
resulting in no submit log or SNAPSHOT file update in the goldos pool.
As a result of this, the "marking" of the GOLDOS_BL12 milestone was a
rev behind for these three files.  One of them appears to have been
caught and at least partially fixed (fixed in PT but not the gold
SNAPSHOT) between PTOS_BL1 and BL2.

Below are the files affected and the submit comments reflecting the
work that was accidentally dropped in Platinum.

Note that these files have not changed since Gold through MP2, and,
while marked incorrectly, the correct file has been used in the builds
through MP2.  The marking does need to be fixed, but only as of
Platinum, where the files were bco'd for edits, did the incorrect label
make any difference to the product.


These files are still missing the indicated submit in PTOS:

./kernel/io/dec/ws/lk201.c,v    

>  * Revision 1.2.12.5  1994/05/31  20:55:37  Jay_Estabrook
>  * 	Do proper default handling for language and keyboard type.
>  * 	Prevent extraneous informative messages during keyboard resets.
>  * 	[1994/05/31  20:53:35  Jay_Estabrook]

./kernel/io/dec/ws/pcxal.c,v   

>  * Revision 1.1.11.9  1994/05/31  20:55:39  Jay_Estabrook
>  * 	Make informative print permanent, in pcxal_bot_init().
>  * 	[1994/05/31  20:53:44  Jay_Estabrook]


This one appears to have been caught between PTOS_BL1 & BL2, and
fixed for Platinum, but should still be checked in gold & support:

./kernel/data/pcxal_data.c,v

>  * Revision 1.1.8.5  1994/05/31  20:55:26  Jay_Estabrook
>  *    Make "kb_getc" entry in pcxal_softc[0] be set to "pcxal_getc"; this
>  *     entry is used to process keyboard input *before* interrupts are
>  *     enabled, typically from "getchar" or "gets" calls.
>  *    [1994/05/31  20:53:21  Jay_Estabrook]


------- End of Forwarded Message