From: Lennart Borgman <lennart.borgman@gmail.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: Sebastien Vauban <sva-news@mygooglest.com>,
Eli Zaretskii <eliz@gnu.org>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Emacs trunk binary on Dropbox
Date: Tue, 1 Oct 2013 18:22:39 +0200 [thread overview]
Message-ID: <CANbX366n8tL9iyAmRst=E6yq+=fC8ZyTcawpxkdf3rBh6W+uoQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0gEon5S+CY6y_Exa5+d7azJGbKujdLTGRHqGJqWgtML4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Must not that revision number be available somewhere in the mirror?
On Oct 1, 2013 6:09 PM, "Dani Moncayo" <dmoncayo@gmail.com> wrote:
> >> 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
>
>
[-- Attachment #2: Type: text/html, Size: 1633 bytes --]
next prev parent reply other threads:[~2013-10-01 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86vc1htogy.fsf@somewhere.org>
[not found] ` <mailman.3202.1380616171.10748.help-gnu-emacs@gnu.org>
[not found] ` <86li2d5qfi.fsf@somewhere.org>
[not found] ` <CAH8Pv0hNWOa6vzSMSOM45-3+cg1Jt4BHZVZsMXCS0NqHgYhofw@mail.gmail.com>
2013-10-01 16:01 ` Emacs trunk binary on Dropbox Eli Zaretskii
2013-10-01 16:08 ` Dani Moncayo
2013-10-01 16:22 ` Lennart Borgman [this message]
2013-10-01 16:36 ` Andreas Schwab
2013-10-01 17:48 ` Eli Zaretskii
2013-10-02 3:00 ` Stephen J. Turnbull
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANbX366n8tL9iyAmRst=E6yq+=fC8ZyTcawpxkdf3rBh6W+uoQ@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).