From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 2/3] doc: added guidelines on dpdk documentation Date: Fri, 3 Jul 2015 10:54:24 +0100 Message-ID: <20150703095424.GB7548@bricha3-MOBL3> References: <1435845053-17203-1-git-send-email-john.mcnamara@intel.com> <1435845053-17203-3-git-send-email-john.mcnamara@intel.com> <1986693.jIPruNIANr@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 8E6062C72 for ; Fri, 3 Jul 2015 11:54:29 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1986693.jIPruNIANr@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jul 02, 2015 at 06:20:39PM +0200, Thomas Monjalon wrote: > 2015-07-02 14:50, John McNamara: > > +* Use one sentence per line in a paragraph, i.e., put a newline character > > + after each period/full stop. > > What about adding this? > Only blank line will generate a newline. > > I think breaking lines at end of sentence is more important than > wrapping at 80 char, because it will help to keep patches > readable. > +1 to this. I believe that one sentence per line should be the default wrapping policy and only wrap if lines are very, very long. The why I like this approach is that changes tend to be sentence-based, and so having a sentence per line makes for much cleaner diffs when updating - thereby making review easier. /Bruce