Mark D. Baushke wrote: > Derek Price <[EMAIL PROTECTED]> writes: > > >Peter Backes wrote: > > >>On 21 Apr 2005 at 10:02, Derek Price wrote: > >> > >>>I really want to make this the default behavior, even after an > >>>upgrade. Would this do the trick for you? > >> > >>What do you mean exactly? new->use_commit_id = true instead of > >>false, i.e. have commit IDs written even for old repositories after > >>an update? I'd not recommend this. It violates the principle of > >>least astonishment (like the current solution). However, at least it > >>was better than the current situation. > > >I'm not sure I believe that. I think most people would prefer to not > >have to jump through any hoops to see new features enabled, especially > >when dealing with feature releases, and I don't think all that many > >people run RCS inside their CVS repositories anymore. Any dissenting > >opinions other than Peter's out there? > > > I am given to understand that WebCVS and ViewCVS can run 'rcs' commands > like rlog as a way to glean information out of the local repository > without running 'cvs' commands on the ,v files.
Okay, but the threads you cite seem to indicate that they have dealt with the problems by passing -q into RCS or tweaking their parsers. I still don't see any reason not to enable commitds by default on feature. Regards, Derek
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bug-cvs mailing list Bug-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/bug-cvs