[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

1966.0. "mroe Re: defunct files (pmap.c)" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Nov 30 1995 11:25

Date Of Receipt: 	30-NOV-1995 10:34:46.18
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  30-Nov-1995 1032"
To: 	winchell@DEC:.zko.flume
CC: 	mansour@zso.dec.com, odehelp@DEC:.zko.flume, bstevens@DEC:.zko.flume
Subj: 	mroe Re: defunct files (pmap.c)

Dave, please don't undefunct this file until we understand why it was
defuncted, and what you're trying to achieve exactly.

It was submitted defunct in CLUSTWAV3OS by Brian_Stevens

thanks...	-josh

------- Forwarded Messages

Return-Path: winchell@tlaser.zk3.dec.com 
Delivery-Date: Wed, 29 Nov 95 18:06:30 -0500
Return-Path: winchell@tlaser.zk3.dec.com
Received: from alpha.zk3.dec.com by flume.zk3.dec.com; 
(5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA12838; Wed, 29 Nov 1995 18:06:18 -0500
Received: from btlaser.zk3.dec.com by alpha.zk3.dec.com; 
(5.65v3.2/1.1.8.2/20May95-1022AM)
	id AA08467; Wed, 29 Nov 1995 18:06:15 -0500
Received: from localhost by tlaser.zk3.dec.com; (5.65v3.2/1.1.8.2/06Mar95-1016A
M)
	id AA19565; Wed, 29 Nov 1995 18:06:00 -0500
Message-Id: <9511292306.AA19565@tlaser.zk3.dec.com>
To: odehelp@tlaser.zk3.dec.com
Cc: winchell@tlaser.zk3.dec.com
Subject: defunct files
Date: Wed, 29 Nov 95 18:06:00 -0500
From: winchell@tlaser.zk3.dec.com
X-Mts: smtp


When I try to bco pmap.c in a sanbox backed by the clutwav3os tree
I get the following:

jibe.zk3.dec.com[865] bco pmap.c

[ ./kernel/arch/alpha/pmap.c ]
bco: no checkout allowed: ./kernel/arch/alpha/pmap.c is defunct




How can I get past this?  The file should not be marked defunct.


thanks,
dave



------- Message 2

Return-Path: mansour@zso.dec.com 
Delivery-Date: Wed, 29 Nov 95 18:23:43 -0500
Return-Path: mansour@zso.dec.com
Received: from alpha.zk3.dec.com by flume.zk3.dec.com; 
(5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA14819; Wed, 29 Nov 1995 18:23:31 -0500
Received: from slugbt.zso.dec.com by alpha.zk3.dec.com; 
(5.65v3.2/1.1.8.2/20May95-1022AM)
	id AA08723; Wed, 29 Nov 1995 18:23:11 -0500
Received: from localhost by slugbt.zso.dec.com; (5.65/DECwest-OSF-Nov-11-93)
Message-Id: <9511292323.AA05640@slugbt.zso.dec.com>
To: winchell@zk3.dec.com
Cc: odehelp@zk3.dec.com
Subject: Re: defunct files 
In-Reply-To: Your message of "Wed, 29 Nov 95 18:06:00 EST."
             <9511292306.AA19565@tlaser.zk3.dec.com> 
Date: Wed, 29 Nov 95 15:23:10 -0800
From: mansour@zso.dec.com
X-Mts: smtp



   If you accidently defuncted this file by mistake,
   in your own sandbox and on your private branch or setname,
  just outdate your branch of the file with:
  
   bcs -o <file>

   If the file is defunct in the submit tree, and you
   are positive that this is the file you want
   to apply some changes to, you must undefunct it first,
   i.e. change the state of the defunct file's revision, from
   "defunct" to "Exp", and  have it available to check_out, with bco.

   from a sandbox back to the submit tree where the file'revision
   is defunct :

   undefunct <file>
   bco <file> 
   aply your changes ...
   bci ...
   bsubmit ... 


/Rima

------- End of Forwarded Messages




T.RTitleUserPersonal
Name
DateLines