From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bastien Newsgroups: gmane.emacs.devel Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req. Date: Sat, 04 Jan 2014 10:42:46 +0100 Message-ID: <87mwjct755.fsf@bzg.ath.cx> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87fvp6bdd9.fsf_-_@ktab.red-bean.com> <8761q1ljny.fsf@gmail.com> <87lhyxqztz.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1388828580 26908 80.91.229.3 (4 Jan 2014 09:43:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jan 2014 09:43:00 +0000 (UTC) Cc: Thierry Volpiatto , Michael Albinus , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 04 10:43:07 2014 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 1VzNl3-0007rq-Pj for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 10:43:05 +0100 Original-Received: from localhost ([::1]:53690 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzNl3-0006Ew-DK for ged-emacs-devel@m.gmane.org; Sat, 04 Jan 2014 04:43:05 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57445) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzNkv-0006Dy-S7 for emacs-devel@gnu.org; Sat, 04 Jan 2014 04:43:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VzNkp-0003At-3p for emacs-devel@gnu.org; Sat, 04 Jan 2014 04:42:57 -0500 Original-Received: from mail-wi0-x22a.google.com ([2a00:1450:400c:c05::22a]:61348) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzNko-0003Ao-Sc for emacs-devel@gnu.org; Sat, 04 Jan 2014 04:42:51 -0500 Original-Received: by mail-wi0-f170.google.com with SMTP id hq4so1221707wib.5 for ; Sat, 04 Jan 2014 01:42:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type; bh=FBCznu5BpEDyscwzWDGUNHXodYH/1oz6B8O6u5g4gyE=; b=Lm9qPVLw6iw2ME+7aVmQIWQtMlC3GiFeTbJJv/K2Y6I5EWMOFkqmNA/3zUHrQsW8kz 0kjCpXbkLNcgjhfvrKilLDv75r+DDm2X0TlO0DcQ0Aa5CEhOxPatrGUKdXquDrsTIrIr 640nvzoZZAgLLXziiUOWFKRhsCx5JNGv6zj+SueQK1jB+kfKk0KptxITVo0F65YewKob Cmsx+7bOqPTKM4EUG9Nhv7I0oC7UQq0qGbo7QqNpyacnq5Gk0kFDyxtJHHeD9aN3qW9V EmFWNy0HAJ8o1YQNRoKvX1Fn4erB5UE115a84KuWU2wVALMKsEXsu9p+WqvPWsN4MIqQ 0LAQ== X-Received: by 10.180.21.204 with SMTP id x12mr5070477wie.45.1388828569812; Sat, 04 Jan 2014 01:42:49 -0800 (PST) Original-Received: from bzg.localdomain (mar75-2-81-56-68-112.fbx.proxad.net. [81.56.68.112]) by mx.google.com with ESMTPSA id md9sm6818956wic.1.2014.01.04.01.42.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Jan 2014 01:42:48 -0800 (PST) Original-Received: by bzg.localdomain (Postfix, from userid 1000) id 20AC21C2063E; Sat, 4 Jan 2014 10:42:46 +0100 (CET) In-Reply-To: (Stefan Monnier's message of "Fri, 03 Jan 2014 09:48:08 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::22a 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:167265 Archived-At: Stefan Monnier writes: > Please let's not rehash old arguments: the tarball contains many files > that are generated, so it would be trivial to include the "git log" > output in it. How would we handle fixing in such generated logs? By revising the git history through rebasing? Not a rhetorical question, just curious, as I do have a problem with the current way Org generates its ChangeLogs. -- Bastien