Whoever sent this should post to [EMAIL PROTECTED]
Anyway, IIRC, you should be able to parse the stdin of the loginfo script to see
the log message (and then some). From what I gather, you'd like to commit this
message into another file? If so, if you follow the advice given in Cederqvist
(regarding using CVS within a loginfo script for another purpose) and throw the
"cvs commit ChangeLog" into the background, you're not guaranteed that this'll
occur atomically with the primary commit.
Here's a couple of things you can do to guarantee it's atomicity:
1. use rcs to commit the ChangeLog
2. create a temporary module within the repository; symlink the ChangeLog,v file
into the temporary module; "cvs checkout" and "cvs commit" this temporary module
(not in the background); remove the temporary module. Ensure that the temporary
module name is unique across simultaneous commits.
Note that I use the word "atomic" in a loose way. The commit will by no means
be atomic with regards to hardware failures and such.
Noel
[EMAIL PROTECTED] on 05/25/2000 04:02:18 AM
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: loginfo to log all changes
Hi, collegues.
How can I log all log messages which are stored in the source file by
the -m option in one global log file ? Some GNU projects have a log file
called ChangeLog, where all changes of the project are logged in. I know
the file loginfo and I start an application to edit the global log file,
but then the log message isn't stored in the repository or the developer
has to write the log message twice: with the -m option and with the
application. Ist there a way to get the log info of the -m option in a
script ?
thanks for help
Wolf
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
