The problem here is that edit comments are one-per-file while checkin comments
are one-per-command-line (or one-per-directory when using local CVS).
Noel
[EMAIL PROTECTED] on 2000.10.13 12:52:44
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: Edit comments?
I would expect the edit comment to be the default commit message:
- It appears in the editor when it comes up.
- It becomes the commit message when given an empty -m option.
- It is overridden by a non-empty -m option.
--- Forwarded mail from [EMAIL PROTECTED]
I had thought a little about this at one point. IIRC, this would involve no
more than adding an extra subfield in fileattr and extending the protocol a
little. I don't think this is that much work since the protocol can be extended
easily without breaking older clients/servers (but you may not have the new
feature if you use older clients/servers).
One thing to ensure is that special characters in the new subfield must be
escaped properly.
Using the comments for checkin may need some more thought. For example, will
the edit comments be appended to the checkin comments or will they replace
checkin comments?
--- End of forwarded message from [EMAIL PROTECTED]
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.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
