From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Newsgroups: gmane.emacs.devel Subject: Re: Emacs 23.2.94 pretest Date: Wed, 23 Feb 2011 17:28:29 -0700 Message-ID: <86hbbup976.fsf@gmail.com> References: <87aahva31q.fsf@gmail.com> <87y6567ihx.fsf@stupidchicken.com> <19813.18711.4000.254620@gargle.gargle.HOWL> <87oc627ey3.fsf@stupidchicken.com> <19813.28612.567000.982556@gargle.gargle.HOWL> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1298507330 11037 80.91.229.12 (24 Feb 2011 00:28:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 24 Feb 2011 00:28:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 24 01:28:46 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PsP4X-0001Rc-8f for ged-emacs-devel@m.gmane.org; Thu, 24 Feb 2011 01:28:45 +0100 Original-Received: from localhost ([127.0.0.1]:35324 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PsP4W-0004CO-M5 for ged-emacs-devel@m.gmane.org; Wed, 23 Feb 2011 19:28:44 -0500 Original-Received: from [140.186.70.92] (port=56021 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PsP4P-0004BU-4l for emacs-devel@gnu.org; Wed, 23 Feb 2011 19:28:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PsP4N-0001Zv-Kv for emacs-devel@gnu.org; Wed, 23 Feb 2011 19:28:36 -0500 Original-Received: from mail-vw0-f41.google.com ([209.85.212.41]:44783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PsP4N-0001Zo-Hl for emacs-devel@gnu.org; Wed, 23 Feb 2011 19:28:35 -0500 Original-Received: by vws13 with SMTP id 13so9614vws.0 for ; Wed, 23 Feb 2011 16:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version:content-type; bh=PkoB+tOoWenlgAwreqLOLnO//wPdWexvL+UdP+JMp/8=; b=RLN+k+AQekw5C+oLVvd5dLuVy3Ur09+T9d2vGZHcc+tab3Tp+cXrue6N/S4QLywZSL ObYicO56w9fd7d/evPpCYg27ptaYAO5ggbV7WS6SMw8HREGH1lhJUeM9d9pKjMvE3bx3 hqPC31X0cROR27CB1wp6ccgcJkktOe108YTrQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type; b=LI4sxcivCwFRbHXk8jiyl43YxoBIZA3WfXA2SEpaYZpVOonbcvTZYnp5O8nCmdt2BP PUm8i705x1yzwMdKzXMlUWBkC/gZJxkwlXCjwWFiU8hw9+Re+WPo/iYSFeHIle5u5rPG 2ohNFgiTks76h6HYk7dFMb/fL7ufHCFaqckqE= Original-Received: by 10.52.161.67 with SMTP id xq3mr314063vdb.112.1298507314374; Wed, 23 Feb 2011 16:28:34 -0800 (PST) Original-Received: from localhost (71-208-142-116.hlrn.qwest.net [71.208.142.116]) by mx.google.com with ESMTPS id i14sm3893496vcr.11.2011.02.23.16.28.32 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Feb 2011 16:28:33 -0800 (PST) In-Reply-To: (Lennart Borgman's message of "Wed, 23 Feb 2011 21:41:59 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (windows-nt) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.212.41 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:136420 Archived-At: Lennart Borgman writes: > Is there anything that prevents naming the uploaded binaries after the > bzr rev number/id? Just the .zip file? Or the 24.0.50 folder contained in it? I agree that we should identify the weekly trunk snapshot Sean builds with a bzr revision id. However, this should be an automated process executed when running `make dist' and not some manual (error-prone) renaming. Once I finish the Python cleanup I am working on right now, I want to try to extend the `make dist' rule to incorporate this. The sole purpose of this would be to tie the weekly Windows snapshot to a revision in bzr for troubleshooting. Since the bzr revision is not unique across branches it is not very useful for general Emacs builds unless one can be sure the source of the build is the trunk. I will think more about this, maybe there is a solution that works for all builds on all systems. Christoph