[Top][All Lists]

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

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

From: Rahul Bhargava
Subject: Re: [patch #4573] Fix for keyword expansion problem/mis-feature during commit
Date: Tue, 15 Nov 2005 13:38:04 -0800
User-agent: Mozilla Thunderbird 1.0.5 (Windows/20050711)

Hi Mark -

We are already aware of this feature. If you read the
initial post, we are not talking about disabling keywords
or excluding certain keywords using CVS from feature

We are talking about the mis-feature that causes CVS to
bump up revisions when a user commits a file which only
differs in keywords.

The proposed patch preserves the admin's ability to use
keywords without creating spurious versions on the tree.

We speak for 100s of companies using CVS today who would
like to get the submitted patch as an optional feature in
CVS. No we are not asking that default behaviour be changed.
Iff an admin wants the behaviour we outlined in the initial
post they can enable ignoring of keywords during classification
phase of commit.

If an admin/user wants to use $..$ for their own needs they do
not have to turn on the feature! All works as before.  Again this
is being proposed as an optional behavior, no need to change
semantics if you don't  want.


Mark D. Baushke wrote:

Follow-up Comment #13, patch #4573 (project cvs):

FEATURE branch already has the ability to disable
RCS keyword expansion either selectively, or altogether.

To disable it totally, use the CVSROOT/config line:


to disable just the expansion of $Id$ and $Header$, use
the CVSROOT/config line:


So, a CVS administrator who wants to use $Id: ... $ lines
for their own purposes and not have RCS expansion change
anything on them would just need to put


and not worry about it as all modules in the CVS project
would no longer do expansion of that RCS keyword.


Reply to this item at:


 Message sent via/by Savannah

Rahul Bhargava,
CTO, WANdisco
(650) 242-8352
Mountain View, CA

reply via email to

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