From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 1D3F5292D for ; Tue, 16 May 2017 16:21:01 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2017 07:21:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,349,1491289200"; d="scan'208";a="102358441" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by fmsmga005.fm.intel.com with ESMTP; 16 May 2017 07:21:00 -0700 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.170]) by IRSMSX101.ger.corp.intel.com ([163.33.3.153]) with mapi id 14.03.0319.002; Tue, 16 May 2017 15:20:59 +0100 From: "Mcnamara, John" To: Thomas Monjalon CC: "Iremonger, Bernard" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v1] doc: change doc line length limit in contributors guide Thread-Index: AQHSywF6okJQQIgYjkm/1pOmNUWL7aH3B5dA Date: Tue, 16 May 2017 14:20:58 +0000 Message-ID: References: <1494511780-5732-1-git-send-email-john.mcnamara@intel.com> <8CEF83825BEC744B83065625E567D7C224D5D178@IRSMSX108.ger.corp.intel.com> <5820031.igZ32l5vOD@xps> In-Reply-To: <5820031.igZ32l5vOD@xps> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzY1ZTY1ZTEtZWFkMi00MGU4LWJkOGEtZjExZGNhMDNmMzhmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkxYQnNFV0hoMUEyVG5tcWRaTFhzVFkyeCt4WndUWklxOWpFKzBuU2dhVHc9In0= dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v1] doc: change doc line length limit in contributors guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2017 14:21:02 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Friday, May 12, 2017 10:24 AM > ,,, > > > The current DPDK "single sentence per line plus wrap at ~120 characters= " > > guideline is unusual, not supported by editors and, with rare > > exceptions, not followed by anyone. > > > > As such I think the guidelines should reflect how people actually > > write docs and submit patches, which is wrapping at 80 characters. >=20 > I am OK with 80 characters. > However, I think we should keep trying to explain that it is better to > wrap at the end of a sentence. >=20 > Example: > This long sentence with a lot of words which does not mean anything will > wrap at 80 characters and continue on the second line. Then a new sentenc= e > starts and ends on the third line. >=20 > It would be better like that: > This long sentence with a lot of words which does not mean anything will > wrap at 80 characters and continue on the second line. > Then a new sentence starts and ends on the third line. This is essentially the same problem as the current guideline: that this is an artificial way of writing text, it isn't supported by editors, and is unlikely to be followed in practice. The first example is the way people write text and the way text is submitte= d in patches so the guidelines should reflect this. John