Re: Proposing a tiny change

David> Stephen J. Turnbull wrote: >> >>>>>>> David> Could y'all add to the procedures for striking a David> "latest-beta" baseline something that would add David> xemacs-patch-date="2001-11-12T13:14Z" (or something David> similar) to file 'version.sh'? David> It should be pretty simple automated scripting. David> Maybe it's me that isn't understanding. If I checkout the David> source tree using "-r r21-5-latest-beta" today I get 21-5-3 David> (unless it changed last night). Am I guarenteed that there David> will be *no* changes applied until you announce a 21-5-4? No. David> That I will *never* need to do cvs update until there is a David> new beta? Depends on what you want to do. If a bug fix was commited that you wanted to verify, then you'll have to update (or apply the corresponding patch sent to xemacs-patches). You determine when and why you have to update :-) David> If the last two statements above are *not* true, then I'm David> asking for a finer grained indication that I could feedback David> so y'all know precisely what source I'm working with when I David> report a problem. In the past I thought I had seen "cvs Report the cvs update (or checkout) command line you used and the time and time zone you ran it. That determines what you'll get. version.sh can't possible have that information. Hope this helps, Adrian David> update -r r21-5-latest-beta" report some updates. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/