info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Order of operations during commit when using a CVS server


From: Reinstein, Shlomo
Subject: Order of operations during commit when using a CVS server
Date: Thu, 17 Oct 2002 08:47:17 +0200

Hi,

Until now, I've been using CVS with a locally-mounted repository. When I did
"cvs commit", it used to first run the command specified in
CVSROOT/commitinfo for every directory that had to be committed, and then it
launched the editor to enter the log message (only if the commands had a
good exit value for all directories).
Now, I am using a CVS server, and that behavior is reversed: CVS first
launches the editor so that I can enter a log message, and only afterwards
it runs the command from the CVSROOT/commitinfo. The result is that I
sometimes find that I entered the log message for nothing, because as soon
as I exit the editor, it fails because of the commands in
CVSROOT/commitinfo.
Is this a CVS bug, or am I doing something wrong? (I am also the owner and
admin of the repository on the server.)

Thanks,
Shlomo






reply via email to

[Prev in Thread] Current Thread [Next in Thread]