avoiding / forcing experimental packages [Re: Pushing new vc towards regular packages tree]

I would still rather figure which packages are in this area (and which are, on the contrary, deemed stable) from the contents of cvs itself in some uniform, well- defined way, without ad- hoc means such as chasing pointers to mailing list archive items containing information for humans only. That is, to have clear conventions and procedure, how, at my option, retrieve from cvs and stick to current experimental, or current stable version of given package. An old issue, already raised at least on Fri, 07 Jul 2006 21:48:00 +0400 (<09lkr5mhm7.fsf(a)mo.msk.ru&gt;, <branching in packages?>). Please consider developing and using such a conventions - on both vc and other packages. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta