Re: Emacs trunk binary on Dropbox

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 1 Oct 2013 11:12:24 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: "help-gnu-emacs@gnu.org list" <help-gnu-emacs@gnu.org>
> 
> > Tiens, I now don't see any Bazar revision anymore:
> >
> >   ╭────
> >   │ emacs-bzr-version is a variable defined in `version.el'.
> >   │ Its value is nil
> >   │
> >   │ Documentation:
> >   │ String giving the bzr revision from which this Emacs was built.
> >   │ The format is: [revno] revision_id, where revno may be absent.
> >   │ Value is nil if Emacs was not built from a bzr checkout, or if we could
> >   │ not determine the revision.
> >   ╰────
> >
> > Is this normal?
> 
> I guess this is due to the fact that now I'm making my builds from the
> git repository [1], instead of the bzr branch.
> 
> Anyway, if you want to know the bzr revno associated with a binary,
> just look at the archive name, as explained in the file
> "snapshots/README":
> 
>   The archives in this directory are named according to this pattern:
> 
>      emacs-rREVNO-YYYYMMDD-API-bin.zip
> 
>   where:
>     * REVNO is the bzr revision (of the trunk branch) that was built.
>     * YYYYMMDD is the commit date of the above revision.
>     * API is the host OS API (always "w32" for now).

That's too bad, because now report-emacs-bug will not show the bzr
revision, and whoever reads the bug report has no idea from which zip
file the binary came.

Please reconsider the decision, or provide some way for your builds to
report the bzr revision.  TIA.