From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel,gmane.emacs.windows Subject: Re: [h-e-w] emacs-20110725 windows binaries Date: Thu, 28 Jul 2011 01:15:11 +0200 Message-ID: References: <87pqky34qs.fsf@gmail.com> <871uxbn1h3.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1311808543 3930 80.91.229.12 (27 Jul 2011 23:15:43 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 27 Jul 2011 23:15:43 +0000 (UTC) Cc: help-emacs-windows@gnu.org, emacs-devel@gnu.org To: Sean Sieger Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 28 01:15:40 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QmDKF-00084t-Qj for ged-emacs-devel@m.gmane.org; Thu, 28 Jul 2011 01:15:39 +0200 Original-Received: from localhost ([::1]:55442 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmDKF-0001Bo-Aw for ged-emacs-devel@m.gmane.org; Wed, 27 Jul 2011 19:15:39 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50787) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmDKB-000141-PK for emacs-devel@gnu.org; Wed, 27 Jul 2011 19:15:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmDKA-0008H4-Oe for emacs-devel@gnu.org; Wed, 27 Jul 2011 19:15:35 -0400 Original-Received: from mail-ey0-f174.google.com ([209.85.215.174]:62858) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmDK8-0008GW-FM; Wed, 27 Jul 2011 19:15:32 -0400 Original-Received: by eyx24 with SMTP id 24so3674220eyx.19 for ; Wed, 27 Jul 2011 16:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=4cLShuQsawGgeema3bkLqHtkc+Uh4fcm6O//AFu40FU=; b=cHQcGg7skvNtTDG/T+WyOU68LzW1hv2SyxsPsIvAL5AdAwxYNIMF/4NOgBRDAMYeFZ lZ59zniwb82N9ofhM1HrTNra2yhFrvWi8XBuUX/6hsj3JjNrQxeBv5os04EelHnoqg2K si48ARzfYtHZfucNjU0z65G9jdLDCFlHQ+qog= Original-Received: by 10.213.8.205 with SMTP id i13mr155087ebi.87.1311808531287; Wed, 27 Jul 2011 16:15:31 -0700 (PDT) Original-Received: by 10.213.20.81 with HTTP; Wed, 27 Jul 2011 16:15:11 -0700 (PDT) In-Reply-To: <871uxbn1h3.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.215.174 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142409 gmane.emacs.windows:5047 Archived-At: On Wed, Jul 27, 2011 at 18:16, Sean Sieger wrote: > Lennart Borgman writes: > > =C2=A0 =C2=A0On Wed, Jul 27, 2011 at 12:06, Dani Moncayo wrote: > > =C2=A0 =C2=A0> Given a concrete (built) Emacs, are there a way to know th= e bzr > =C2=A0 =C2=A0> revision that was used to build it? > > =C2=A0 =C2=A0No, currently it is not possible. I have suggested that it s= hould be, > =C2=A0 =C2=A0however. And I have added that to my patched version of > =C2=A0 =C2=A0Emacs+EmacsW32. (Unfortunately I have not time at the moment= to build > =C2=A0 =C2=A0that version.) > > Yes, currently it is possible. =C2=A0Open the file in the Emacs distribut= ion > that you'd like to work on. =C2=A0In the mode line, you will see the > Bzr- 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.