Re: [patch #4573] Fix for keyword expansion problem/mis-feature during commit

[Derek R. Price]

Arthur Barrett wrote:
> In particular your original patch was not suitable for inclusion in
> CVSNT (or probably for cvs 1.12) as it has a hardcoded list of keywords,

This isn't why, but we did decide against including this patch.  Our
reason for deciding against this was that we don't want to include
anything in CVS that might automatically throw away work done by the
user.  As you said, as things stand, the -ko option may be used to
retrieve the original prior to Rahul's patch being applied.  Afterwards,
it becomes possible for the automation to throw away an intentional,
albeit probably misguided, change.  I still don't understand why Rahul's
customer can't just stop running scripts that change the keyword contents.

History is here:
<https://savannah.nongnu.org/patch/?func=detailitem&item_id=4573>.

A man went to a doctor and said, "Doctor, when I do this it hurts."  The
doctor took one look and said, "Well, stop doing that!"

Derek

-- 
Derek R. Price
CVS Solutions Architect
Get CVS support at Ximbiot <http://ximbiot.com>!
v: +1 248.835.1260
f: +1 248.835.1263
<mailto:address@hidden>