From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Armando Vega <armando@greenhost.nl>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v2 1/1] xl man page cleanup and fixes
Date: Wed, 31 May 2017 14:48:49 +0100 [thread overview]
Message-ID: <22830.51649.843338.684864@mariner.uk.xensource.com> (raw)
In-Reply-To: <631356df-5d27-17d0-ca8c-8deb2ea4748a@greenhost.nl>
Armando Vega writes ("Re: [PATCH v2 1/1] xl man page cleanup and fixes"):
> It could be from how I broke the lines to 80 chars, it kept the spaces
> between the words at the end, could that be the problem? I can watch out
> for that in the future.
Yes, that will be it.
However, in general, it is not very useful to rewrap lines
automatically in documents such as this one which are going to be
reformatted by a text formatter.
Rather, if a line gets too long, break it at a phrase or sentence
boundary. That means that future diffs are much more readable.
http://rhodesmill.org/brandon/2012/one-sentence-per-line/
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-05-31 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 18:01 [PATCH 0/1] xl man page cleanup and fixes proposal Armando Vega
2017-05-29 18:01 ` [PATCH 1/1] xl man page cleanup and fixes Armando Vega
2017-05-30 9:19 ` Wei Liu
2017-05-30 14:08 ` Ian Jackson
2017-05-30 14:20 ` Julien Grall
2017-05-30 14:09 ` [PATCH 0/1] xl man page cleanup and fixes proposal Ian Jackson
2017-05-31 6:30 ` [PATCH v2 " Armando Vega
2017-05-31 11:01 ` Ian Jackson
2017-05-31 12:12 ` Armando Vega
2017-05-31 6:30 ` [PATCH v2 1/1] xl man page cleanup and fixes Armando Vega
2017-05-31 9:46 ` Wei Liu
2017-05-31 12:10 ` Armando Vega
2017-05-31 12:18 ` Wei Liu
2017-05-31 13:48 ` Ian Jackson [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=22830.51649.843338.684864@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=armando@greenhost.nl \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.