>> It [Update -A] also reverts any local -k options back to the repository defaults.
Good thing to know given it quietly does that in addition to merging HEAD of trunk with your workspace. >> I don't see what's dangerous or confusing about it, it's a quick way to throw away any local configuration and get back to a "normal" working directory. To a person we use the repository configuration so reverting configurations back to "normal" is not an issue nor is anybody tinkering with config files without knowing what they are changing. What I find dangerous is that you could update -A and later commit without realizing you just added branch changes to the trunk. You could operate for days before the problem was realized. What I find confusing is that it quietly carries out three tasks that we never use individually let alone together. Granted that's specific to our selected strategy. Thanks for the additional insight. _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
