CVS Diffs [Was Making xemacs-21.5.3+/i686-pc-cygwin]

David> Suppose on Monday I do "cvs checkout -r21-5-latest-beta" If you are using -r r21-5-latest-beta, and make no modifications to the sources, then all you need to do is submit Installation. Installation gives the version numbers we need to construct the specific tag (eg, r21-5-3) which tells us everything about the XEmacs sources you built. Details: The way r21-5-latest-beta is constructed is 1. I check out and package r21-5-x for distribution. 2. I tell CVS to tag the versions in my workspace as r21-5-x. CVS does not get confused if someone checks in changes between steps 1 and 2. It uses the versions recorded in CVS/Entries. 3. I tell CVS to move the tag r21-5-latest-beta from wherever it is to have exactly the same versions as r21-5-x. Again, CVS will not get confused. Thus, although that tag will move with the release of r21-5-(x+1), we can reconstruct the tag r21-5-x from the version information. You can even update your workspace; the old XEmacs binary still contains a sufficient description of the state of the sources in its version no. I misunderstood your original post, and thought you were talking about following HEAD (eg, the result of cvs update -A, or a fresh checkout with no tag requested). This does require additional information, such as a reasonably precise date or a diff, to characterize the sources you built. Then I got interested in exactly how CVS handles the diff.... -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."