RE: `about-emacs' - what about the revno?

[Drew Adams]

> > If the "revno" is important info for identifying an Emacs 
> > build, then perhaps we should include it in such user-facing info.
> >
> > If not, then perhaps developers could refer in some other
> > way (by date?) to the code that contains a given fix.
> 
> This has come up before, but the discussion was inconclusive (IIRC)
> because of 2 reasons:
> 
>   . revno is not unique: two different branches can have the same
>     revno for two very different code bases
> 
>   . revision-id, an alternative method of specifying a revision, _is_
>     unique, but it's long and a mouthful:
> 
>             address@hidden
> 
> In general, a bugfix should appear in the ChangeLog files with the bug
> number, so you should be able to track bugfxes that way.

OK, thanks.

But please see the "If not..." part above.  I am interested in knowing which
upcoming Windows binary will have a particular fix (e.g. identified by "revno
101110").  When communicating with bug-report filers, a date is perhaps more
useful than just a revno (and users should not need to dig into change logs).
Some users might be able to do something with a revno, but a date should be of
some help to any user.