Dear colleagues,
I am fairly new to cvs administration, although I use
cvs constantly. I would like to know how I can
configure my cvs server so that it rejects commits
that have empty log messages, i.e. when one tries
cvs commit -m myfile.txt
myfile.txt won't be committed in the repository.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ivan Ivanov [EMAIL PROTECTED] writes:
Dear colleagues,
I am fairly new to cvs administration, although I use
cvs constantly. I would like to know how I can
configure my cvs server so that it rejects commits
that have empty log messages, i.e.
Hello:
I'm trying to set up a cvs server under cygwin on a Windows Millennium box. Everything
works fine except that I cannot commit changes to the repository. I can do ckeckouts,
import new modules, add files directories... but committing changes fails. This is
the error message I get:
cvs
Title: Reports generation in CVS
I have to generate report which displays the name of branch or tag, date on which it was created, the author name and the name of the module on week basis for a project. For eg- The project duration was of three months. Now the report has to be generated on
Tyler wrote:
For various reasons, i believe that promoting RELEASE up to
HEAD is a
good idea (mostly related to low level cvs management and
administration).
Question 1: am i right to want to do this?
From what you have described, I think so.
Question 2: is there a better way to do
At 09:02 AM 6/2/2004, Ramanuj Singh wrote:
name of branch or tag, date on which it was created, the author name and
the name of the module
CVS stores that information in the history file (cvs history -aT). A script
that parses the output has to be aware that individual files can be tagged,
not
Ivan Ivanov wrote:
So my quiestions are
1) What regular expression should stay in my verifymsg
file
To expand on Mark's reply a little: the regular expression is used to
determine which script, if any, will be run, based on the directory you're
checking in. For example, if you had:
^projectX
Ramanuj Singh wrote:
I have to generate report which displays the name of branch
or tag, date on which it was created, the author name and the
name of the module on week basis for a project. For eg- The
project duration was of three months. Now the report has to
be generated on week basis
Frederic Brehm wrote:
One method that I use is to have a special module named scm
that contains
scripts for tag, release, and other configuration management
operations. I teach the developers to use the scripts instead
of the raw
CVS commands. It's easy to get them to use the scripts if
Jim.Hyslop writes:
I've never had much luck with the history command. I just tried it on some
files, and according to 'cvs history', I have applied only nine tags in the
last year. I *know* I have applied more than that.
History only records rtag commands (which tag modules), not regular tag
10 matches
Mail list logo
