[The fact that one must use the official name is documented, but it is
an interesting question whether it should be an error if .cvsrc
contains something besides an official name.  Silently ignoring such
lines allows one to use the same .cvsrc file with different versions
of CVS which accept different sets of commands, but I'm not sure that
is important.  After all, you can still use a .cvsrc which includes
the commands they have in common. -kingdon]

Date: Fri, 23 Jan 1998 09:58:39 -0500 (EST)
From: Justin Vallon <vallon@Bear.COM>
To: bug-cvs@prep.ai.mit.edu
Subject: Bug report


>Submitter-Id:   net
>Originator: 	 Justin Vallon
>Organization:
net
>Confidential:  no 
>Synopsis:	
.cvsrc file silently ignores aliases
>Severity:	non-critical 
>Priority:	low 
>Category: 	doc 
>Class:		doc-bug 
>Release:	cvs-1.9
>Environment:
    	
-
System: HP-UX pearl B.10.20 A 9000/712 2010599992 two-user license


>Description:
	
The description of the cvsrc file fails to mention that the "commands" should
not be aliases.  That is, the following .cvsrc file does not work, and does 
not give an error or warning:

co -l


>How-To-Repeat:
	
Should be totally reproducible.

>Fix:
	
Suggestion:

1)  Allow aliases to appear in .cvsrc file.

or

2)  If the first word of a .cvsrc line is not 'legal', give a warning:

       cvs:  warning:  .cvsrc gives option for unknown command 'blatz'.


--
*******************************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, offer or
agreement or any information about any transaction, customer account or account
activity contained in this communication.
*******************************************************************************