[Top][All Lists]

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

[patch #4573] Fix for keyword expansion problem/mis-feature during commi

From: Derek Robert Price
Subject: [patch #4573] Fix for keyword expansion problem/mis-feature during commit
Date: Fri, 4 Nov 2005 19:31:42 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

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

The data loss you refer to only occurs in the user's sandbox.  The change is
committed to the repository.  If the original user or another user were to
checkout/update the file in -kb or -ko modes, then they would see the data
they committed.  In fact, this could be used as a workaround for the problem
you describe - if only the user in question wants to see their local changes
inside key-values after commit, then they should mark text files -ko on
checkout/update and binaries -kb.  If all users should see what the user
committed inside key-values, then `cvs add' or `cvs admin' should be used to
mark the files default keyword mode as -ko or -kb.  Either of these is even a
more fine-grained solution than yours, since it allows this behavior to be
selected on a file-by-file basis.

If I recall the documentation correctly, keywords are currently defined as
being updated at checkout time, but I suspect updating them at commit time is
or was considered a feature by some, since it means that no update is needed
after a commit of newly added keywords to have the key-value substituted
correctly locally.  If this is not documented behavior, then it probably
should be.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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