From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "Fixed bug #XYZZY" Date: Mon, 08 Dec 2014 22:30:16 +0200 Message-ID: <838uihyjdz.fsf@gnu.org> References: <83iohmxdr6.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1418070650 14433 80.91.229.3 (8 Dec 2014 20:30:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2014 20:30:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 08 21:30:43 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 1Xy4x9-0000jU-2O for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2014 21:30:43 +0100 Original-Received: from localhost ([::1]:36006 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xy4x8-0001vu-If for ged-emacs-devel@m.gmane.org; Mon, 08 Dec 2014 15:30:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54360) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xy4wy-0001vk-Qa for emacs-devel@gnu.org; Mon, 08 Dec 2014 15:30:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xy4wt-0007JP-Ba for emacs-devel@gnu.org; Mon, 08 Dec 2014 15:30:32 -0500 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:41265) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xy4wt-0007J9-3j for emacs-devel@gnu.org; Mon, 08 Dec 2014 15:30:27 -0500 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NGA00A00612H400@mtaout25.012.net.il> for emacs-devel@gnu.org; Mon, 08 Dec 2014 22:26:09 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NGA002J163KG470@mtaout25.012.net.il>; Mon, 08 Dec 2014 22:26:09 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 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:179457 Archived-At: > From: Stefan Monnier > Date: Mon, 08 Dec 2014 13:33:14 -0500 > Cc: emacs-devel@gnu.org > > > Can we agree to say something in the commit log's summary line about > > the bug essence, in addition to the bug number? Otherwise, the > > summary is not really informative, and you need to look at the bug > > report in the tracker. > > Indeed, the bug number should be on another line. The summary should > describe the change, instead. Of course, if they both fit, it's OK to > put them together. Also remember to use the "bug#NNN" format. So, can we codify something like this: Summary bla-bla summary line. Fixes: bug#NNNNN * src/foobar.c (foobar): Change. * lisp/foobar.el (foo-bar): Change. ?