From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dani Moncayo Newsgroups: gmane.emacs.devel Subject: Re: Emacs trunk binary on Dropbox Date: Tue, 1 Oct 2013 18:08:42 +0200 Message-ID: References: <86vc1htogy.fsf@somewhere.org> <86li2d5qfi.fsf@somewhere.org> <83bo39dlph.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1380643732 22542 80.91.229.3 (1 Oct 2013 16:08:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Oct 2013 16:08:52 +0000 (UTC) Cc: Sebastien Vauban , Emacs development discussions To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 01 18:08: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 1VR2VL-000672-Rt for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 18:08:55 +0200 Original-Received: from localhost ([::1]:59865 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2VL-0007LG-By for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 12:08:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2VH-0007Hq-3c for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:08:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR2VF-0001iD-IR for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:08:51 -0400 Original-Received: from mail-lb0-x229.google.com ([2a00:1450:4010:c04::229]:49640) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2VA-0001fc-9g; Tue, 01 Oct 2013 12:08:44 -0400 Original-Received: by mail-lb0-f169.google.com with SMTP id z5so6204843lbh.0 for ; Tue, 01 Oct 2013 09:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Er0OeEknp7HXAnpxPY+7L4YbE26PlzuM4BVNHoLCsYA=; b=qKhrFxwniCSLi/+t6PtsOFSFn0k8zty0ibpH7BgCDIt09m965paMNOX1F4cY5tbyPW d2YsYOPjHRr2L5ENL+MJM6b/bGrPdTKqGnljPcfNTBo3JJzQWfL6wmglAtwaUteYeyLo Fs/GqmL8WYJ18IayGksWfNbRCoQMQ3iBGTzoh6QsERNOnsKdVGhamaBGsxm7hErvCQzw pYvSYfTl7aLfdMti4vKV5ywt4P8pcywTjDQAsMR8QfPrv7KAQBp9bUoh/5FgEZ4nyFoH fRNPIHFSoXRu/8nYnFzeHwG7FRWePF1QnmgsG8JZkcRjCdwXmAj+zRTOIf9MKrP4elIR 1EiQ== X-Received: by 10.112.161.105 with SMTP id xr9mr2147825lbb.40.1380643722648; Tue, 01 Oct 2013 09:08:42 -0700 (PDT) Original-Received: by 10.114.176.231 with HTTP; Tue, 1 Oct 2013 09:08:42 -0700 (PDT) In-Reply-To: <83bo39dlph.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c04::229 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:163771 Archived-At: >> 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