From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 7/8] xenalyze: remove traling whitespaces
Date: Fri, 8 May 2015 08:22:08 +0200 [thread overview]
Message-ID: <20150508062208.GC1737@aepfle.de> (raw)
In-Reply-To: <554BA059.2020708@citrix.com>
On Thu, May 07, Andrew Cooper wrote:
> On 07/05/15 11:35, Olaf Hering wrote:
> > Result of "sed -i 's@[[:blank:]]\+$@@' tools/xentrace/xenalyze/xenalyze.c"
> >
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > Cc: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Wei Liu <wei.liu2@citrix.com>
>
> Why not refresh patch 1 using git's --whitespace=fix mode? It would
> save adding whitespace just to remove it again, and also fix up the
> other imported files.
As George said, my intention was to use the sources from hg as is.
My editor marks trailing spaces. But I have another changeset, the
result from running indent(1) on the source. It would have the same
effect. Too bad, the result cant be used as is so I have excluded it
from this series. The manual editing of the result takes some time.
Olaf
next prev parent reply other threads:[~2015-05-08 6:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 10:35 [PATCH v2 0/8] add xenalyze to staging Olaf Hering
2015-05-07 10:35 ` [PATCH v2 1/8] xenalyze: add to tools/xentrace/xenalyze Olaf Hering
2015-05-07 16:45 ` George Dunlap
2015-05-08 5:20 ` Wei Liu
2015-05-11 14:15 ` Olaf Hering
2015-05-11 14:23 ` Ian Campbell
2015-05-11 14:28 ` Olaf Hering
2015-05-11 14:33 ` George Dunlap
2015-05-11 14:47 ` Olaf Hering
2015-05-12 8:45 ` Ian Campbell
2015-05-12 9:09 ` George Dunlap
2015-05-07 10:35 ` [PATCH v2 2/8] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-05-07 16:52 ` George Dunlap
2015-05-08 6:14 ` Olaf Hering
2015-05-08 5:22 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 3/8] xenalyze: print newline after unknown hvm events Olaf Hering
2015-05-07 16:53 ` George Dunlap
2015-05-08 5:22 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 4/8] xenalyze: include odd mmio states in default output Olaf Hering
2015-05-07 16:53 ` George Dunlap
2015-05-08 5:23 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 5/8] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-05-07 17:04 ` George Dunlap
2015-05-08 5:24 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 6/8] xenalyze: handle more events in sched_process Olaf Hering
2015-05-07 17:13 ` George Dunlap
2015-05-07 17:28 ` Andrew Cooper
2015-05-07 17:42 ` George Dunlap
2015-05-12 14:53 ` Dario Faggioli
2015-05-08 5:30 ` Wei Liu
2015-05-08 6:18 ` Olaf Hering
2015-05-07 10:35 ` [PATCH v2 7/8] xenalyze: remove traling whitespaces Olaf Hering
2015-05-07 17:15 ` George Dunlap
2015-05-07 17:26 ` Andrew Cooper
2015-05-07 17:34 ` George Dunlap
2015-05-08 6:22 ` Olaf Hering [this message]
2015-05-08 5:32 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 8/8] xenalyze: remove argp_program_version Olaf Hering
2015-05-07 17:18 ` George Dunlap
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=20150508062208.GC1737@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.