All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Armando Vega <armando@greenhost.nl>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
	ian.jackson@eu.citrix.com
Subject: Re: [PATCH v2 1/1] xl man page cleanup and fixes
Date: Wed, 31 May 2017 13:18:09 +0100	[thread overview]
Message-ID: <20170531121809.c4lygk7j35jznh4i@citrix.com> (raw)
In-Reply-To: <631356df-5d27-17d0-ca8c-8deb2ea4748a@greenhost.nl>

On Wed, May 31, 2017 at 02:10:27PM +0200, Armando Vega wrote:
> I'm not sure I know what you mean, do you mean spaces trailing some of
> the lines?
> 

Yes.

> 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.

We don't want that. Git also complains when applying a patch like that.

Depending on your text editor there are ways to get rid of trailing
white spaces automatically.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-05-31 12:18 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 [this message]
2017-05-31 13:48       ` Ian Jackson

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=20170531121809.c4lygk7j35jznh4i@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=armando@greenhost.nl \
    --cc=ian.jackson@eu.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.