[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Is this a bug?
RE: Is this a bug?
Sat, 19 May 2001 19:21:26 +0100
Yep, spot on. I /do/ have "CVS:" at the start of all the template lines as I
want to provide some comments/recommendations to the user about the log
message they're about to enter. I guess my only workround for this
(admittedly rare) condition is to hack logmesg.c so that my additional
comments get re-presented.
Thanks for the input
From: address@hidden [mailto:address@hidden
Sent: 18 May 2001 19:55
Subject: Re: Is this a bug?
Andy Baker writes:
> After editing a log message during the commit process you quit from the
> editor (eg :q! in vi) the following prompt (correctly) appears.
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for
> remaining dirs
> Action: (continue)
> However, if you select e to re-edit, any template specified in rcsinfo
> doesn't appear to get re-loaded, just the vanilla cvs template.
> Is this a bug or am I missing something?
You're missing something, although it's hard to say what. The message
that's written into the temp file for the editor consists of any
previous message, any rcsinfo template (unless it's the same as the
previous template) , and the standard template. After editing, the temp
file is read and lines beginning with "CVS:" are removed; what remains
becomes the previous message for the next go-round. If what remains is
empty (or is just a blank line), or if the file is unmodified (based on
its timestamp), you get the message. So, the only ways I can think of
to get your result is that either your rcsinfo template lines start with
"CVS:" or you deleted the template and saved the result before quiting
from the editor; otherwise, the template would have been read into the
previous message and thus preserved.
Something COULD happen today. And if anything DOES,
by golly, I'm going to be ready for it! -- Calvin
Info-cvs mailing list
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents. We cannot accept liability for any breaches of
confidence arising through use of email. Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions. We will not accept responsibility for any commitments
made by our employees outside the scope of our business. We do not warrant
the accuracy or completeness of such information.