From: Lennart Borgman <lennart.borgman@gmail.com>
To: Sean Sieger <sean.sieger@gmail.com>
Cc: help-emacs-windows@gnu.org, emacs-devel@gnu.org
Subject: Re: [h-e-w] emacs-20110725 windows binaries
Date: Thu, 28 Jul 2011 01:15:11 +0200 [thread overview]
Message-ID: <CANbX364N+fHGr2YSBXkfVMYKo+Ha+S9bVgmdwJLM_mVP2r4iLg@mail.gmail.com> (raw)
In-Reply-To: <871uxbn1h3.fsf@gmail.com>
On Wed, Jul 27, 2011 at 18:16, Sean Sieger <sean.sieger@gmail.com> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
> On Wed, Jul 27, 2011 at 12:06, Dani Moncayo <dmoncayo@gmail.com> wrote:
>
> > Given a concrete (built) Emacs, are there a way to know the bzr
> > revision that was used to build it?
>
> No, currently it is not possible. I have suggested that it should be,
> however. And I have added that to my patched version of
> Emacs+EmacsW32. (Unfortunately I have not time at the moment to build
> that version.)
>
> Yes, currently it is possible. Open the file in the Emacs distribution
> that you'd like to work on. In the mode line, you will see the
> Bzr-<revno> you are looking for.
>
> But I think, Lennart, you gotta use the development branch to see this.
> I don't understand why you need the revision number if you're not using
> it---it just doesn't make sense to me.
As Eli explained this is not the revision number of the binary.
Oh, yes. It makes sense. I provide both the revison number of the
development branch and my patched branch.
next prev parent reply other threads:[~2011-07-27 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 12:48 emacs-20110725 windows binaries Sean Sieger
2011-07-27 10:06 ` Dani Moncayo
2011-07-27 10:09 ` Lennart Borgman
2011-07-27 16:16 ` Sean Sieger
2011-07-27 16:23 ` [h-e-w] " Eli Zaretskii
2011-07-28 0:10 ` Sean Sieger
2011-07-28 0:17 ` Lennart Borgman
2011-07-28 0:48 ` Sean Sieger
2011-07-27 23:15 ` Lennart Borgman [this message]
2011-07-27 23:41 ` [h-e-w] " Sean Sieger
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=CANbX364N+fHGr2YSBXkfVMYKo+Ha+S9bVgmdwJLM_mVP2r4iLg@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=sean.sieger@gmail.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).