From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req. Date: Fri, 03 Jan 2014 01:53:05 -0800 Message-ID: <52C68881.8090406@dancol.org> References: <20140102095347.6834E381D0C@snark.thyrsus.com> <87lhyxqztz.fsf@gmx.de> <87vby1a0hf.fsf@bzg.ath.cx> <3209902.RR9Upzp9ei@descartes> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1388742799 20468 80.91.229.3 (3 Jan 2014 09:53:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 3 Jan 2014 09:53:19 +0000 (UTC) Cc: Bastien , Michael Albinus , Thierry Volpiatto To: =?UTF-8?B?UsO8ZGlnZXIgU29uZGVyZmVsZA==?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 03 10:53:25 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 1Vz1RV-0005er-Dc for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2014 10:53:25 +0100 Original-Received: from localhost ([::1]:48856 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz1RV-0003nm-1M for ged-emacs-devel@m.gmane.org; Fri, 03 Jan 2014 04:53:25 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz1RM-0003nh-K9 for emacs-devel@gnu.org; Fri, 03 Jan 2014 04:53:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vz1RG-0006db-Fi for emacs-devel@gnu.org; Fri, 03 Jan 2014 04:53:16 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:35373) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz1RG-0006dV-1U for emacs-devel@gnu.org; Fri, 03 Jan 2014 04:53:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=K1ShjX3ElrNPXpwMz9S0Afw41JZ0qD/FbJqRfuSxIo0=; b=TEaBiz0rCemO5MWnCP1jK8GbyAEoRxvGUKfYRYpR5x88ZAo/4m21NIQVf1g4jAO9u//uNXIZDslTG1FAtyi901aBR7Ya6PO39qkDOLueRSOUpebBz0Iw2wdbKj8iZnwRl14PnAiD215Bn4CsnaX3reIkKTWd98dhXh8GMoKfXrKgKbOgIEvOvJjZJSWmtv2LbZkmRx6A3X6fCLmOr5G78KfHIInU1kkL9tjAykLVrgdL1CY/MCuGh00PAQqEke+ihC4wCdq6EBhYu1+Y15+0V4ifdzKuZdeRfSQ8LuUJWD1pKId//EhdvQ7ymH7g8qI1f8atymTBmk/9sNH/5IvCfg==; Original-Received: from [12.144.179.211] (helo=[10.10.1.82]) by dancol.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Vz1RD-0006uA-9N; Fri, 03 Jan 2014 01:53:07 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <3209902.RR9Upzp9ei@descartes> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:167133 Archived-At: On 01/03/2014 01:35 AM, Rüdiger Sonderfeld wrote: > On Friday 03 January 2014 10:17:00 Bastien wrote: >>> Another question is, whether we still want to write ChangeLogs manually, >>> or whether we want to extract them from commit comments. That's not such >>> easy, see all the "fix typo" comments. >> >> I'm all for writing them manually, it's a useful exercise. >> >> IMHO git commit messages should reproduce ChangeLogs, not the >> other way around. > > Generating them from commit messages would do exactly that. Right now most > people copy all or at least parts of the ChangeLog entry to the commit message > anyway. I agree that the format is useful and I absolutely agree that the > commit message should not necessarily only be a copy of the ChangeLog entry. > > But those points are not really an obstacle or argument against auto- > generation of the ChangeLog _files_ from the commit messages It's a lot safer to fix an error in ChangeLog than to interactively rebase and force-push a new history. Would this automated ChangeLog generation system be tolerant of manual ChangeLog editing? If we're going to have ChangeLog files anyway, we're still going to have to deal with merging. Since we have to write change descriptions in any case and since we already have mature tools for making ChangeLog additions, we might as well retain the current system. It would be nice, though, to auto-fill commit messages based on ChangeLog deltas. By the way: git-merge-changelog from gnulib looks useful.