From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4C0EC1386F2 for ; Tue, 11 Aug 2015 01:26:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3CA3F14344; Tue, 11 Aug 2015 01:25:56 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3987C1432D for ; Tue, 11 Aug 2015 01:25:55 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZOyK8-0002oc-JD for gentoo-dev@lists.gentoo.org; Tue, 11 Aug 2015 03:25:52 +0200 Received: from ip98-167-165-199.ph.ph.cox.net ([98.167.165.199]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Aug 2015 03:25:52 +0200 Received: from 1i5t5.duncan by ip98-167-165-199.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Aug 2015 03:25:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: Referencing bug reports in git Date: Tue, 11 Aug 2015 01:25:48 +0000 (UTC) Message-ID: References: <1439128706.40b3fd64ec9c5d6d94f0f0897740bc77622c24a1.xmw@gentoo> <55C75F19.90201@gentoo.org> <20150809215605.27ae6427@pomiot> <20150810004409.59637bea9aefd3f045b67614@gentoo.org> <20150810004044.76dda6e6@pomiot> <20150810021601.cdcae7226373ecd0d284086a@gentoo.org> <21959.62847.967959.705319@a1i15.kph.uni-mainz.de> <55C7F833.6040408@gentoo.org> <20150810181730.3ef13778@caribou.gateway.pace.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip98-167-165-199.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT af87825) X-Archives-Salt: 357c0e47-420c-4f91-b08a-a184ec310274 X-Archives-Hash: 2b77f37346c00713833a31367aff14d3 Ryan Hill posted on Mon, 10 Aug 2015 18:17:30 -0600 as excerpted: > On Mon, 10 Aug 2015 12:25:58 +0000 (UTC) > Duncan <1i5t5.duncan@cox.net> wrote: >> What about: >> >> * bug number in summary strongly recommended > > Making the bug number in the summary manditory or strongly encouraged > leads to wonderful commit messages like: > > --- > cat-pkg: Fix bug #504321. Ideally, it'd be something a bit more informative (here taking Gordon's points about the previously suggested B#): cat-egory/semi-long-package-name: fix amd64-fbsd build error G-504321 > I would like to see this be more common: > > --- > cat-pkg: Make the thingy work again > > Gentoo-Bug: https://bugs.gentoo.org/504321 *(or 504321 Idon'tcarewhich) > ---- > > If we're limiting the summary to 1 line, 70-75 chars, manditory > cat/package and bug number there's not a lot of room to summarize in. Note that a bug number would fit in your above summary very easily, omitting nothing, as it's only ~35/75 length. Even with my somewhat longer cat/pkg example with the longest arch- keyword I could quickly find, there's still room to indicate at minimum build vs runtime error, with the gentoo bug number reference for anyone who might find it interesting enough to look further than the one-line. People can then either select and klipper-popup (adding my usual trigger method to the others people have mentioned), or read the longer description for the full bug URL to click, if they prefer. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman