On Tue, May 09, 2006 at 04:13:41PM -0400, Nathan Gray wrote: > Perhaps the sticky tags are only created during bootstrap? I'll play > around with this a little bit more and send more info if I find > anything.
With a little more investigation, and some IRC discussion, Lele and I decided the sticky tags are caused by CVS, not tailor. Thus the tag-entries = False attribute for CVS repositories is never being triggered. With some more investigation, I found this page: http://www.cvsnt.org/manual/html/Sticky-tags.html which states that: If you check out a certain revision (such as 1.4) it will become sticky. Subsequent cvs update commands will not retrieve the latest revision until you reset the tag with cvs update -A. However: People often want to retrieve an old version of a file without setting a sticky tag. This can be done with the -p option to checkout or update, which sends the contents of the file to standard output. I tried this out and discovered that the CVS/Entries file is then not updated with the revision number of the file. Lele suggested that the best fix would be to have tailor checkout using the -p option if tag-entries is False, and update the CVS/Entries file(s) via tailor. So, I think that is the current plan. -kolibrie _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
