Forcing Log message during commit
Hafeez Mohammad
Is there a option where I can force all the CVS users
to use "-m" option while commiting files in the
repository. CVS should abort the commit when there is
no log message.
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
_______________________________________________
Info-cvs mailing list
Info...@gnu.org
http://mail.gnu.org/mailman/listinfo/info-cvs
Kostur, Andre
some scripts that will reject commits if there isn't at least one non-empty
line. If you're interested (or anybody else), I can make them available, or
email them to you. But as a hint, what you're looking for is to change the
'verifymsg' file in CVSROOT to run a script of your choosing. If your
script returns a 1, CVS will reject your checkin, and send whatever output
your script has back to the CVS client. If your script returns a 0, CVS
will accept the checkin. Oh yeah, one wrinkle: WinCVS will put in a comment
of "no message" if you leave the dialog box blank, so be sure to make your
script check for that as well...
Hafeez Mohammad
How to remove Empty directories from CVS repository.
I am using the following commands
cvs remove dirname
cvs commit -m "Removing the empty directory" dirname
The above commands doesn't work.
I know that cvs -P update will Prune the Empty
directories from the checked out but I want to
remove them from the CVS repository.
Any Suggestions ?
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Teala Spitzbarth
CVS does not actually 'version' the directories -
so there is no way to 'commit' changes to them.
You have two choices, and to the best of my understanding
the salient factor in choosing between them is whether or not you will
ever have to reproduce your source from a time when the directory
*was* there (i.e. a old tag)
1) if you have tags, or need to be able to reproduce old
versions of your source
you must only run cvs remove on the files, commit the
changes
and rely on -P to prune the empty directory from fresh
pulls.
The files are stored in an Attic subdirectory for
retrieval on tagged
pulls.
2) if you have no tags, and truly, truly never need to
reproduce anything
from that directory - then you can go into the
repository and do
a file system level remove of the directory. If you
have files in
the attic within that directory - I wouldn't do this...
when its removed
it is gone, you can never go back!
I personally only do number 2 if a developer makes a mistake and adds
new files into an
incorrect directory name... that is the only situation where I know I
will never
have to reproduce a build with those files....
Cheers,
Teala
-----Original Message-----
From: Hafeez Mohammad [mailto:hafe...@yahoo.com]