All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1] doc: change doc line length limit in contributors guide
Date: Fri, 12 May 2017 18:04:04 +0530	[thread overview]
Message-ID: <ef21cbb8-6cdd-d36e-cda0-742cd81d6108@nxp.com> (raw)
In-Reply-To: <1494511780-5732-1-git-send-email-john.mcnamara@intel.com>

Sorry for the triviality, once again:

On Thursday 11 May 2017 07:39 PM, John McNamara wrote:
> The DPDK documentation guidelines state that lines should be wrapped as
> follows:
>

[..]

>
> -     Here is an example sentence.
> -     Long sentences over the limit shown below can be wrapped onto
> -     a new line.
> -     These three sentences will be joined into the same paragraph.
> +* Lines in literal blocks **must** by less than 80 characters since
                                     ^^^^^
                 "...blocks **must** be less than ..."

> +  they aren't wrapped by the document formatters and can exceed the page width
> +  in PDF documents.

[...]

 From [1]:
"Quis custodiet ipsos custodes?".

"DPDK custodes" :) (Sorry for my pathetic latin)

[1] http://dpdk.org/ml/archives/dev/2017-May/065655.html

-
Shreyansh

      parent reply	other threads:[~2017-05-12 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 14:09 [PATCH v1] doc: change doc line length limit in contributors guide John McNamara
2017-05-11 15:23 ` Thomas Monjalon
2017-05-11 16:11   ` Mcnamara, John
2017-05-11 17:18     ` Thomas Monjalon
2017-05-11 17:31       ` Iremonger, Bernard
2017-05-12  9:10         ` Mcnamara, John
2017-05-12  9:23           ` Thomas Monjalon
2017-05-16 14:20             ` Mcnamara, John
2017-05-16 14:37               ` Thomas Monjalon
2017-05-22  6:44               ` Yuanhan Liu
2017-06-04 10:26                 ` Thomas Monjalon
2017-05-12 12:34 ` Shreyansh Jain [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef21cbb8-6cdd-d36e-cda0-742cd81d6108@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.