[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
small bug when adding binary file to a specific release number
From: |
fcoa |
Subject: |
small bug when adding binary file to a specific release number |
Date: |
Thu, 14 Aug 2003 05:14:03 +0200 |
User-agent: |
IMP/PHP IMAP webmail program 2.2.0 |
Inside my working directory, I add a new file and commit it:
cvs add -kb file.bin
cvs commit file.bin
cvs status file.bin
----->sticky option -kb shows
Up to here, its all right, but when you force a revision number when
committing, the -kb for binary type file disappears:
cvs add -kb file.bin
cvs commit -r 1.5 file.bin
cvs status file.bin
----->There are no sticky options, neither here nor the repository.
I have reproduced it in cvs 1.11.x in windows and linux, and the latest CVS
version(1.12.1) in linux.
I discovered it when learning CVS. I suppose almost nobody has make this, since
is not the usual way to use CVS, but fixing it could save a lot of headackes in
the future.
Paco Arjonilla
Madrid (Spain)
- small bug when adding binary file to a specific release number,
fcoa <=