[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[patch #4573] Fix for keyword expansion problem/mis-feature during commi
Derek Robert Price
[patch #4573] Fix for keyword expansion problem/mis-feature during commit
Thu, 16 Feb 2006 14:17:22 +0000
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20060111 Firefox/188.8.131.52
Follow-up Comment #19, patch #4573 (project cvs):
Pat, in your use cases, the user cannot "[control the server] metadata",
spuriously or otherwise. The server will still substitute the correct
keyword information on checkout, provided the user did not actually delete
the keywords from the file, which this patch would not prevent.
The difference is that, currently, if a misguided user checks in a change
after editing the keyword information in the file, it can still be recovered.
After this patch, this would no longer be possible. The "very simple
guarantee" guarantee we are attempting to provide is that user changes cannot
be permanently lost.
Also, your second example, where a bug fix from a contractor contains
differing RCS keyword information can be fixed by any of several simple
procedural fixes: 1. Have your contractor send a diff rather than copies of
every file, 2. import drops from your contractor into a special tree and
generate the same diffs yourself, 3. use vendor branches to import code drops
from your contractor.
Reply to this item at:
Message sent via/by Savannah