From: Oleg Endo <oleg.endo@t-online.de>
To: Sebastian Perta <sebastian.perta@renesas.com>,
'Jakub Jelinek' <jakub@redhat.com>,
Nick Clifton <nickc@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PING [PATCH] RX movsicc degrade fix
Date: Mon, 12 Feb 2018 12:21:00 -0000 [thread overview]
Message-ID: <1518438067.10908.1.camel@t-online.de> (raw)
In-Reply-To: <000001d3a3f1$8cf26ce0$a6d746a0$@renesas.com>
On Mon, 2018-02-12 at 11:06 +0000, Sebastian Perta wrote:
> > > 1) there should be a space between * and the filename
> The spaces are there (see the changelog), the renesas mail server
> removes them sometimes
You might want to send around your patches as email attachments. Â That
avoids formatting issues.
Cheers,
Oleg
next prev parent reply other threads:[~2018-02-12 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 14:10 Nick Clifton
[not found] ` <20180209182349.GL5867@tucnak>
2018-02-12 11:06 ` Sebastian Perta
2018-02-12 11:19 ` Jakub Jelinek
2018-02-12 12:21 ` Oleg Endo [this message]
2018-02-12 12:49 ` Jakub Jelinek
2018-02-12 13:27 ` Sebastian Perta
2018-02-12 13:49 ` Jakub Jelinek
2018-02-12 13:37 ` Sebastian Perta
2018-02-12 16:49 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2018-02-06 13:43 Sebastian Perta
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=1518438067.10908.1.camel@t-online.de \
--to=oleg.endo@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=nickc@redhat.com \
--cc=sebastian.perta@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).