From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Emacs trunk binary on Dropbox Date: Tue, 1 Oct 2013 18:22:39 +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: multipart/alternative; boundary=f46d043c80ea898a1704e7b05c16 X-Trace: ger.gmane.org 1380644622 2655 80.91.229.3 (1 Oct 2013 16:23:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Oct 2013 16:23:42 +0000 (UTC) Cc: Sebastien Vauban , Eli Zaretskii , Emacs-Devel devel To: Dani Moncayo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 01 18:23:46 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 1VR2jg-0001l6-Mr for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 18:23:44 +0200 Original-Received: from localhost ([::1]:60005 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2jg-0001Kg-5f for ged-emacs-devel@m.gmane.org; Tue, 01 Oct 2013 12:23:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48253) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2ij-0008UU-7q for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:22:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR2ih-0007PF-U2 for emacs-devel@gnu.org; Tue, 01 Oct 2013 12:22:45 -0400 Original-Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]:62344) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2ig-0007Oq-0x; Tue, 01 Oct 2013 12:22:42 -0400 Original-Received: by mail-we0-f180.google.com with SMTP id u57so7417245wes.25 for ; Tue, 01 Oct 2013 09:22:39 -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=A9f7Kc3UnIBvqJGBKuU7fEe707upXjaixc9/KyvnPq8=; b=xJXkKLs4idqlQlA9+yegojPJk9SL04spO3cCbzEV6apDzFui1cXukKLWTU7l0VNmkp HX4q2CSEpngyZa8CGDNMByCYWSbRsxet07JWoak2xZ2HzQzBWNHjdwVgVh+/nOrvgoJL 4dSMpOfPI7PwvObHDs/ub2RVethftzxBDP6WwiuHQlTxCQUZ7ezgdIpO7RaC+jPBKbml jV8OtmIJpgCCub2hcCqGbcCP9daFRfa4DmLCiIP7hoJroCy3bfxqXSpE9QFrxCSCNY6I CbwKF6IeU9QEaFu0MzNPb4kelTYyS4Ij+2A5GkUPS36LP8pGYgzHsLPOjHx4IN2lQoAX 2PvQ== X-Received: by 10.180.90.19 with SMTP id bs19mr19204138wib.15.1380644559618; Tue, 01 Oct 2013 09:22:39 -0700 (PDT) Original-Received: by 10.194.240.41 with HTTP; Tue, 1 Oct 2013 09:22:39 -0700 (PDT) Original-Received: by 10.194.240.41 with HTTP; Tue, 1 Oct 2013 09:22:39 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c03::234 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:163773 Archived-At: --f46d043c80ea898a1704e7b05c16 Content-Type: text/plain; charset=UTF-8 Must not that revision number be available somewhere in the mirror? On Oct 1, 2013 6:09 PM, "Dani Moncayo" 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 > > --f46d043c80ea898a1704e7b05c16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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":
>>
>> =C2=A0 The archives in this directory are named according to this = pattern:
>>
>> =C2=A0 =C2=A0 =C2=A0emacs-rREVNO-YYYYMMDD-API-bin.zip
>>
>> =C2=A0 where:
>> =C2=A0 =C2=A0 * REVNO is the bzr revision (of the trunk branch) th= at was built.
>> =C2=A0 =C2=A0 * YYYYMMDD is the commit date of the above revision.=
>> =C2=A0 =C2=A0 * 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<= br> > file the binary came.
>
> Please reconsider the decision, or provide some way for your builds to=
> report the bzr revision. =C2=A0TIA.

It would be nice if I could specify the bzr revno manually, for
example as a parameter to "configure" or "make", becaus= e having to
keep using bzr just for this little thing would also be too bad.

--
Dani Moncayo

--f46d043c80ea898a1704e7b05c16--