From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs trunk binary on Dropbox Date: Tue, 01 Oct 2013 19:01:30 +0300 Message-ID: <83bo39dlph.fsf@gnu.org> References: <86vc1htogy.fsf@somewhere.org> <86li2d5qfi.fsf@somewhere.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1380643373 18241 80.91.229.3 (1 Oct 2013 16:02:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Oct 2013 16:02:53 +0000 (UTC) Cc: sva-news@mygooglest.com, emacs-devel@gnu.org To: Dani Moncayo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 01 18:02:56 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VR2PX-0000of-Nx for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 18:02:55 +0200 Original-Received: from localhost ([::1]:59815 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2PX-0003nR-93 for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 12:02:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2OH-0001xP-JT for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:01:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR2OB-00075w-PD for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:01:37 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:56871) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2OB-00072t-Ht for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:01:31 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0MTZ00F00Z49I500@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Tue, 01 Oct 2013 19:01:29 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MTZ00FMZZ6GB4B0@a-mtaout23.012.net.il>; Tue, 01 Oct 2013 19:01:29 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 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:163770 Archived-At: > Date: Tue, 1 Oct 2013 11:12:24 +0200 > From: Dani Moncayo > Cc: "help-gnu-emacs@gnu.org list" >=20 > > Tiens, I now don't see any Bazar revision anymore: > > > > =E2=95=AD=E2=94=80=E2=94=80=E2=94=80=E2=94=80 > > =E2=94=82 emacs-bzr-version is a variable defined in `version.e= l'. > > =E2=94=82 Its value is nil > > =E2=94=82 > > =E2=94=82 Documentation: > > =E2=94=82 String giving the bzr revision from which this Emacs = was built. > > =E2=94=82 The format is: [revno] revision_id, where revno may b= e absent. > > =E2=94=82 Value is nil if Emacs was not built from a bzr checko= ut, or if we could > > =E2=94=82 not determine the revision. > > =E2=95=B0=E2=94=80=E2=94=80=E2=94=80=E2=94=80 > > > > Is this normal? >=20 > 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. >=20 > 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": >=20 > The archives in this directory are named according to this patter= n: >=20 > emacs-rREVNO-YYYYMMDD-API-bin.zip >=20 > where: > * REVNO is the bzr revision (of the trunk branch) that was buil= t. > * 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 t= o report the bzr revision. TIA.