Package: cvs
Version: 1:1.12.9-10
Severity: minor

When I add a directory to a repository from computer A,
then commit the change, fill the new directory and commit it.

Then, in preparation for doing cvs update to get the new files
onto computer B, I do (on computer B):

mkdir new_dir
cvs add new_dir

I get the following misleading message:

$ cvs add English French
[EMAIL PROTECTED]'s password:
Directory /home/gpk/CVSROOT/0501course/04_2005/English added to the repository
Directory /home/gpk/CVSROOT/0501course/04_2005/French added to the repository
$

The directories were NOT just added to the repository.
They were already there.
And, just to prove that the directory really was in the repository
before the preceeding add operation:

$ cvs update
[EMAIL PROTECTED]'s password:
cvs server: Updating .
cvs server: Updating English
U English/rdst10h.htm
U English/reader.py
cvs server: Updating French
U French/01.txt
U French/02.txt
U French/03.txt
U French/Doyle.txt
U French/ref.dat
$




-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages cvs depends on:
ii  debconf                     1.4.30.11    Debian configuration management sy
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libpam-runtime              0.76-22      Runtime support for the PAM librar
ii  libpam0g                    0.76-22      Pluggable Authentication Modules l
ii  zlib1g                      1:1.2.2-3    compression library - runtime

-- debconf information:
  cvs/rotatekeep: 7
* cvs/badrepositories: create
  cvs/pserver_warning:
  cvs/rotatekeep_nondefault: no
  cvs/rotate_individual: true
  cvs/pserver_repos_individual: true
  cvs/pserver_setspawnlimit: false
  cvs/rotatekeep_individual: 7
  cvs/pserver_repos: all
* cvs/pserver: false
  cvs/cvs_conf_is_dead:
* cvs/repositories: /export/big/CVSROOT
  cvs/pserver_spawnlimit: 400
  cvs/rotatehistory: no


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to