[EMAIL PROTECTED] on 2000.10.05 15:53:43
>Agreed entirely. The only bit of this whole watch on/watch off (Karate
>Kid, anyone?) discussion that I find odd is on the non-technical level,
>which you don't really address above, viz. that *any* user on the
>project located *anywhere* can cause my sandbox to behave differently
>than it did yesterday (when next I perform an update, of course). The
>thrust of my comments is this: I'd prefer "any user" to be replaced with
>"a designated user", and "anywhere" with...well, location doesn't really
>matter. :-)
What about getting rid of "cvs watch on/off" altogether and making this feature
a configuration parameter inside CVSROOT/config? The main difference I see is
the granularity of "cvs watch on/off". However, I think teams tend to use "cvs
watch on/off" for the entire repository, anyway. In fact, I think there may be
a feature (or bug) in which new modules do not get "cvs watch on" if the team
already deems all modules to have "cvs watch on".
Noel
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
