RE: next emacs version?

[Drew Adams]

> >  * files.el (directory-listing-before-filename-regexp): Use
> >  stricter matching for iso-style dates, to avoid false matches
> >  with date-like filenames (Bug#5597).
> 
> This is revision 99545, which is before the branch.  So this change
> will be both in Emacs 23.2 and Emacs 24.

OK. Where do you see such info (on the Web site)? That info could be useful in
the future. I'm only interested in HTTP access to such info.

> > The question remains, however, which >, <=, etc. test could 
> > do the job robustly, since the dev version is 24.0.50.1 and the first 
> > corresponding release will be 23.2?
> 
> I think you want `(version<= emacs-version "23.2")'.

Really? 

Won't some builds of 24.0.50.1 have the change and some not? As you say, it
depends whether the build is after revision #99545.

If I use version< 23.2 to distinguish instead, then the same problem occurs:
Some 24.0.50.1 versions will not have the change.

As I said, my main concern it wrt official releases, but "I'm also interested in
advice about testing against an in-development version."

AFAICT, there is no simple solution to that. I think you've pretty much
confirmed that, so at least I know I'm not missing something obvious.

(This release is apparently imminent, so no problem in this particular case.)


We can test for the existence of a var or function. How about being able (in
Lisp) to test for a particular source-code revision, such as #99545, for cases
where there is nothing specific and handy to check (like a var or fn)? Or being
able to test for a particular bug-fix (like #5597)?