[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

981.0. ".BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Thu Oct 06 1994 11:50

Date Of Receipt: 	 6-OCT-1994 10:00:01.04
From: 	WASTED::"[email protected]" "06-Oct-1994 0958"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	.BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman

Dear odehelp,

which one is correct in the following?

.BCSset-shared-set-name OR .BCSset-shared-setname

=============================
mksharedsb(8)                                                   mksharedsb(8)

NAME
  mksharedsb - creates a shared sandbox

SYNOPSIS

  mksharedsb  parfile

::
::

3.  Create the file .BCSset-shared-set-name in the shared sandbox's src
      directory and list the non-defunct files in the correct format with the
      command:

      sed 's/,v.*//' ../logs/SNAPSHOT > .BCSset-shared-setname

      Edit this file, .BCSset-shared-setname, and remove the blank line at
      the top of the file.  Remove files from this list that you don't want
      to submit at this time.
=============================


Thanks,
Sunil.

T.R	Title	User	Personal Name	Date	Lines
981.1	Re: .BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman	SMURF::FILTER	Automatic Posting Software - mail to flume::puck	`Thu Oct 06 1994 12:57`	68
	Date Of Receipt: 6-OCT-1994 11:32:40.31 From: FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE" To: [email protected] CC: [email protected], odehelp@DEC:.zko.flambe, [email protected] Subj: Re: .BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman Sunil, both of these refer to the same thing: .BCSset-shared-set-name OR .BCSset-shared-setname For example, if your default_set of the sandbox is SPEC1170, then the filename is .BCSset-SPEC1170 -josh From [email protected] Thu Oct 6 09:57:45 1994 Delivery-Date: Thu, 06 Oct 94 09:57:48 -0400 Return-Path: [email protected] Received: from abelia.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM) id AA01968; Thu, 6 Oct 1994 09:57:45 -0400 Received: from ds9.unx.dec.com by wasted.zk3.dec.com; (5.65/1.1.8.2/01Sep94-0829AM) id AA21094; Thu, 6 Oct 1994 09:57:22 -0400 Received: by ds9.unx.dec.com; id AA21567; Thu, 6 Oct 1994 09:58:11 -0400 Message-Id: <[email protected]> To: [email protected] Cc: [email protected], [email protected], [email protected] Subject: .BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman Date: Thu, 06 Oct 94 09:58:11 -0400 From: [email protected] X-Mts: smtp Dear odehelp, which one is correct in the following? .BCSset-shared-set-name OR .BCSset-shared-setname ============================= mksharedsb(8) mksharedsb(8) NAME mksharedsb - creates a shared sandbox SYNOPSIS mksharedsb parfile :: :: 3. Create the file .BCSset-shared-set-name in the shared sandbox's src directory and list the non-defunct files in the correct format with the command: sed 's/,v.*//' ../logs/SNAPSHOT > .BCSset-shared-setname Edit this file, .BCSset-shared-setname, and remove the blank line at the top of the file. Remove files from this list that you don't want to submit at this time. ============================= Thanks, Sunil.
981.2	Re: .BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman	SMURF::FILTER	Automatic Posting Software - mail to flume::puck	`Thu Oct 06 1994 12:58`	15
	Date Of Receipt: 6-OCT-1994 11:38:39.16 From: WASTED::"[email protected]" "06-Oct-1994 0834" To: [email protected] CC: [email protected], [email protected], [email protected], [email protected] Subj: Re: .BCSset-shared-set-name OR .BCSset-shared-setname in mksharedsb odeman Sunil, I'll PTT the manpage. The references to the shared set name should all be consistent in their use of dashes, and should all be underlined to indicate it's a variable value rather than something you type literally (in most cases it's underlined, but we missed a few). Mike