From owner-cvs-user  Tue Sep  3 16:21:21 1996
Return-Path: owner-cvs-user
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA03394
          for cvs-user-outgoing; Tue, 3 Sep 1996 16:21:21 -0700 (PDT)
Received: (from peter@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA03223;
          Tue, 3 Sep 1996 16:19:54 -0700 (PDT)
Date: Tue, 3 Sep 1996 16:19:54 -0700 (PDT)
From: Peter Wemm <peter>
Message-Id: <199609032319.QAA03223@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-user
Subject: cvs commit:  src/contrib/cvs/src rcs.c
Sender: owner-cvs-user@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

peter       96/09/03 16:19:54

  Modified:    contrib/cvs/src  rcs.c
  Log:
  Implement a horrible (but simple) hack to allow some control over the
  branch number that is assigned.  This is specifically to support the
  local commit feature of cvsup.  If one sets $CVS_LOCAL_BRANCH_NUM to
  (say) 1000 then branches the local repository, the revision numbers will
  look like 1.66.1000.xx.  This is almost a dead-set certainty that there
  will be no conflicts with version numbers. :-)
  
  (This needs to be something more than an option to 'cvs tag' or 'cvs rtag'
  as various parts of cvs "know" how to automatically branch files (eg: cvs
  add).  Trying to remember state is getting "Too Hard (TM)")
  
  Revision  Changes    Path
  1.2       +14 -2     src/contrib/cvs/src/rcs.c