From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Emacs trunk binary on Dropbox
Date: Tue, 1 Oct 2013 18:08:42 +0200 [thread overview]
Message-ID: <CAH8Pv0gEon5S+CY6y_Exa5+d7azJGbKujdLTGRHqGJqWgtML4g@mail.gmail.com> (raw)
In-Reply-To: <83bo39dlph.fsf@gnu.org>
>> 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.
It would be nice if I could specify the bzr revno manually, for
example as a parameter to "configure" or "make", because having to
keep using bzr just for this little thing would also be too bad.
--
Dani Moncayo
next prev parent reply other threads:[~2013-10-01 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 7:55 Emacs trunk binary on Dropbox Sebastien Vauban
2013-10-01 8:29 ` Dani Moncayo
[not found] ` <mailman.3202.1380616171.10748.help-gnu-emacs@gnu.org>
2013-10-01 8:46 ` Sebastien Vauban
2013-10-01 9:12 ` Dani Moncayo
2013-10-01 16:01 ` Eli Zaretskii
2013-10-01 16:08 ` Dani Moncayo [this message]
2013-10-01 16:22 ` Lennart Borgman
2013-10-01 16:36 ` Andreas Schwab
2013-10-01 17:48 ` Eli Zaretskii
2013-10-02 3:00 ` Stephen J. Turnbull
[not found] ` <mailman.3203.1380618754.10748.help-gnu-emacs@gnu.org>
2013-10-01 9:34 ` Sebastien Vauban
2013-10-01 9:58 ` Dani Moncayo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH8Pv0gEon5S+CY6y_Exa5+d7azJGbKujdLTGRHqGJqWgtML4g@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sva-news@mygooglest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.