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: Setting the value of `emacs-bzr-version' also from a git checkout Date: Sat, 12 Oct 2013 14:04:13 +0200 Message-ID: References: <87a9is6g2a.fsf@igel.home> <87pprokewg.fsf@wanadoo.es> <83iox2rd75.fsf@gnu.org> <87bo2uhie3.fsf@wanadoo.es> <83eh7qra3g.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 1381579457 3336 80.91.229.3 (12 Oct 2013 12:04:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 12 Oct 2013 12:04:17 +0000 (UTC) Cc: =?ISO-8859-1?Q?=D3scar_Fuentes?= , Stefan Monnier , Emacs development discussions To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 12 14:04:22 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 1VUxvh-0006g2-Qp for ged-emacs-devel@m.gmane.org; Sat, 12 Oct 2013 14:04:21 +0200 Original-Received: from localhost ([::1]:58023 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VUxvh-0007no-95 for ged-emacs-devel@m.gmane.org; Sat, 12 Oct 2013 08:04:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36558) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VUxvd-0007ni-Rq for emacs-devel@gnu.org; Sat, 12 Oct 2013 08:04:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VUxvc-00071Z-Nf for emacs-devel@gnu.org; Sat, 12 Oct 2013 08:04:17 -0400 Original-Received: from mail-la0-x22d.google.com ([2a00:1450:4010:c03::22d]:63384) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VUxvb-00071N-8L; Sat, 12 Oct 2013 08:04:15 -0400 Original-Received: by mail-la0-f45.google.com with SMTP id eh20so4339477lab.32 for ; Sat, 12 Oct 2013 05:04:13 -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=00ctiz3/sRN1KE41J90h2U4fUxukpzLXNWDxJisO+zc=; b=GTJ/MRweXzHDqkfefpdEqcAeHSe+kL1L00RhVK0yzonBJY18WdJrsDwq8OWKM1qx9T Zt61FUtbwgFrQ99DAysij2vW5OIcmNZCL72sMYItXkKDXnFuuQcB8T0hE7zk7xdUdcY5 SM8D7XA6ZN1T9la2cMO99Uvz72DLbkndYoJUOqjiF6H8JdEITGBeCPmMbzQD5PAGUSwx Q6UP2RUsAh6fcuVsrvYop2uRpJPpRS5T+/Y6sskJ43+aXx70y9Kf+1hG4eXgyVmiDMaI TGjDmB8DUFQrj5lfkf4m10GUCy6ECDLvamvO/pLwf3TcYPbCutc7ll2TmGRgdQSSv+QX yB+g== X-Received: by 10.152.6.41 with SMTP id x9mr1576239lax.31.1381579453510; Sat, 12 Oct 2013 05:04:13 -0700 (PDT) Original-Received: by 10.114.176.231 with HTTP; Sat, 12 Oct 2013 05:04:13 -0700 (PDT) In-Reply-To: <83eh7qra3g.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22d 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:164144 Archived-At: >> I was even asked to include that revnos in the binaries I publish, see: >> >> http://lists.gnu.org/archive/html/help-gnu-emacs/2013-10/msg00002.html > > There's no such request in that message. There's a question there why > the value of a variable is nil where it wasn't previously, that's all. Sorry, I meant another message on the same thread. This one: http://lists.gnu.org/archive/html/help-gnu-emacs/2013-10/msg00004.html Here is what Sebastien told me: [...] I had taken the habit of displaying the revision number in the window title, so that every screenshot would explicitly display with which version the problem occurred. > Look, you are welcome to make it so the git repo has the relevant > information to recreate also the revision numbers. But when you ask > _others_ to do that job for you, please make sure it's really needed, > and not just a nicety. I'm just proposing something, and the remaining work is tiny. I have no idea who can or know how to do it. Right now I don't even know where is the relevant source code (the one for replicating bzr commits into the git repo). I would not mind to do that change myself, but since it's a trivial change, I think anyone could do it (assuming that you -the maintainers- agree with the proposal). -- Dani Moncayo