From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752855AbdKUGDC (ORCPT ); Tue, 21 Nov 2017 01:03:02 -0500 Received: from smtprelay0173.hostedemail.com ([216.40.44.173]:45225 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751899AbdKUGDB (ORCPT ); Tue, 21 Nov 2017 01:03:01 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::,RULES_HIT:41:355:379:541:599:967:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:2890:2892:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3870:3871:3872:3874:4042:4250:4321:5007:10004:10249:10400:10848:11232:11658:11914:12740:12760:12895:13069:13311:13357:13439:14659:21080:21433:21450:21627:30001:30054:30075:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: shirt63_1a13ce0ab9749 X-Filterd-Recvd-Size: 1633 Message-ID: <1511244177.6989.24.camel@perches.com> Subject: Re: [PATCH v2] checkpatch: allow URL >80 chars From: Joe Perches To: Andreas Brauchli , Andy Whitcroft Cc: linux-kernel@vger.kernel.org Date: Mon, 20 Nov 2017 22:02:57 -0800 In-Reply-To: <1511181605.2384.2.camel@elementarea.net> References: <1511181605.2384.2.camel@elementarea.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.26.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2017-11-20 at 13:40 +0100, Andreas Brauchli wrote: > Allow URL to exceed the 80 char limit for improved interaction in > adaption to ongoing but undocumented practice. > > $ git grep -E '://\S{77}.*' -- '*.[ch]' > > The patch checks that the URL is indeed on its own line in that it > allows a maximal prefix of 3 characters to account for a URL after a > comment (e.g. '// https://...') I think this part is not necessary or that useful. For instance, this style /* some long url */ is pretty common. > As per RFC3986 [1], the URL format allows for alphanum, +, - and . > characters in the scheme before the separator :// as long as it starts > with a letter (e.g. https, git, f.-+). That seems right, thanks. > Recognition of URIs without more context information is prone to false > positives and thus currently left out of the heuristics. OK.