From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5437D139694 for ; Tue, 25 Jul 2017 11:49:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 616761FC052; Tue, 25 Jul 2017 11:49:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C3B361FC03F for ; Tue, 25 Jul 2017 11:49:15 +0000 (UTC) Received: from [10.96.117.34] (public-gprs383514.centertel.pl [37.47.129.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 671023416B4; Tue, 25 Jul 2017 11:49:10 +0000 (UTC) Date: Tue, 25 Jul 2017 13:49:04 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <20170725105921.GA17195@skade.schwarzvogel.de> References: <1500969906.1206.1.camel@gentoo.org> <20170725105921.GA17195@skade.schwarzvogel.de> 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: quoted-printable Subject: Re: [gentoo-dev] [RFC pre-GLEP] Gentoo Git Workflow To: gentoo-dev@lists.gentoo.org,Tobias Klausmann From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= Message-ID: <598613A4-94CD-495F-86A1-4BE26FF2566B@gentoo.org> X-Archives-Salt: bed84901-54c7-48e9-a2fe-3c44caeaca78 X-Archives-Hash: 63d93474c574efde46d46ac5c2f2bd14 Dnia 25 lipca 2017 12:59:21 CEST, Tobias Klausmann = napisa=C5=82(a): >Hi!=20 > >On Tue, 25 Jul 2017, Micha=C5=82 G=C3=B3rny wrote: >> The summary line is included in the short logs (git log -- >> oneline, gitweb, GitHub, mail subject) and therefore should >> provide a short yet accurate description of the change=2E The summary >line >> starts with a logical unit name, followed by a colon, a space and a >> short description of the most important changes=2E If a bug is >associated >> with a change, then it should be included in the summary line as >> #nnnnnn or likewise=2E The summary line must not exceed 69 >> characters, and must not be wrapped=2E > >This limit can be a problem if there's a nontrivial change to the >more than 80 packages in the tree that have more than forty characters >in >cat/pkg[0]=2E Is the only option there to do word-smithing or >making the commit summary less usefu? > >Or do we have a "violate if necessary" agreement regarding that? Yeah, i meant to apply the "must not" to wrapping but "should not" to leng= th=2E Though I suggest you to ellipsize the package name, if it is unambigu= ous enough=2E The problem is that if you exceed the length, the summary will be usually = cut one way or another anyway=2E > > >Regards, >Tobias > >[0]=20 >$ cd /usr/portage >$ ls -d *-*/*|awk '{if (length>=3D40) {print length, $0}}'|sort -n --=20 Best regards, Micha=C5=82 G=C3=B3rny (by phone)