From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] master b6610d5 2/4: emacs-lisp/package.el: Refactor pre-execute prompt Date: Tue, 7 Apr 2015 00:41:09 +0100 Message-ID: References: <20150406102057.929.89886@vcs.savannah.gnu.org> <5522653C.5010608@yandex.ru> <5522F90C.4000201@cs.ucla.edu> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0160b9b01baee3051316d55d X-Trace: ger.gmane.org 1428363690 27119 80.91.229.3 (6 Apr 2015 23:41:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Apr 2015 23:41:30 +0000 (UTC) Cc: emacs-devel To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 07 01:41:28 2015 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 1YfGdy-0001mP-L3 for ged-emacs-devel@m.gmane.org; Tue, 07 Apr 2015 01:41:26 +0200 Original-Received: from localhost ([::1]:42191 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfGdx-0006EP-TQ for ged-emacs-devel@m.gmane.org; Mon, 06 Apr 2015 19:41:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34792) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfGdj-0006Co-7T for emacs-devel@gnu.org; Mon, 06 Apr 2015 19:41:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YfGdi-0006By-7c for emacs-devel@gnu.org; Mon, 06 Apr 2015 19:41:11 -0400 Original-Received: from mail-la0-x22d.google.com ([2a00:1450:4010:c03::22d]:35012) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfGdh-0006Bu-Uz for emacs-devel@gnu.org; Mon, 06 Apr 2015 19:41:10 -0400 Original-Received: by labbd9 with SMTP id bd9so18786743lab.2 for ; Mon, 06 Apr 2015 16:41:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=rhAqsWkbXI06o00JyrdUyoMiVVjuqHMIGTVvSvjqcsM=; b=P7ZzgfzvDMy0RczGU/CCIG0vdhR4lH8BaH718/5BJ5mnbFpsK3HTH8fLRWhpNjGfBA ZLdL4BUn6vrB0zbLiheENKfcRBR+U26YSdUMrj9IKcaEe0hneHDRuuT1WPwm2mtffNod C9xfXcWkvirbMTGVSwtOEpL0FDSPmSITeJ9rpdN0VLppTSFLC04ZxkcwudhejoOyW9fW bkTGy4JHI83iMquU9UxLSSJjpaGkguoZ4tNu37gnv5zOqs+IptMt0CtqmVBhskSdAVRW yq8yjh/yxKCbZVXUC3xshc5CboNk+RrOm0PeWwBfAu5Uh60CEic+bDxvSHaN+1Rw7L09 fODA== X-Received: by 10.152.25.132 with SMTP id c4mr15501579lag.4.1428363669121; Mon, 06 Apr 2015 16:41:09 -0700 (PDT) Original-Received: by 10.25.150.131 with HTTP; Mon, 6 Apr 2015 16:41:09 -0700 (PDT) Original-Received: by 10.25.150.131 with HTTP; Mon, 6 Apr 2015 16:41:09 -0700 (PDT) In-Reply-To: <5522F90C.4000201@cs.ucla.edu> X-Google-Sender-Auth: YstE6Fn0LJLK7qwlk0XDF8XJEJM 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:185057 Archived-At: --089e0160b9b01baee3051316d55d Content-Type: text/plain; charset=UTF-8 > I hope so too, but I'm afraid that some sort of reminder will still be > needed, as not every project uses ChangeLog format for commit messages as > our guidelines suggest, and many people aren't used to the suggested style. > > This is not a new problem: many ChangeLog entries don't follow our > guidelines and someone else tidies them up later, which is a pain for the > "someone else". If we can encourage more-standard commit messages, we can > ease the maintenance burden. > > Attached is a brief commentary on recently-added commit messages, which I've > turned into ChangeLog format using the automated procedure that should be in > place shortly, along with some commentary about possible improvements to > these commit messages. Thanks Paul, that's helpful. Is there a reason why we need the * in the summary line? Can't these be added when the changelog is generated? The summary line is usually short on space. --089e0160b9b01baee3051316d55d Content-Type: text/html; charset=UTF-8

> I hope so too, but I'm afraid that some sort of reminder will still be
> needed, as not every project uses ChangeLog format for commit messages as
> our guidelines suggest, and many people aren't used to the suggested style.
>
> This is not a new problem: many ChangeLog entries don't follow our
> guidelines and someone else tidies them up later, which is a pain for the
> "someone else". If we can encourage more-standard commit messages, we can
> ease the maintenance burden.
>
> Attached is a brief commentary on recently-added commit messages, which I've
> turned into ChangeLog format using the automated procedure that should be in
> place shortly, along with some commentary about possible improvements to
> these commit messages.
Thanks Paul, that's helpful.

Is there a reason why we need the * in the summary line? Can't these be added when the changelog is generated?
The summary line is usually short on space.

--089e0160b9b01baee3051316d55d--