linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze patches for 6.2-rc1
Date: Mon, 12 Dec 2022 09:49:18 -0800	[thread overview]
Message-ID: <CAHk-=wiuqbgRZcotVf93Db4+gcPz8yAhW0mMfNZbEkM66rNB3Q@mail.gmail.com> (raw)
In-Reply-To: <b7ece19c-e50e-0709-7be1-2945883d155b@monstr.eu>

On Thu, Dec 8, 2022 at 2:07 AM Michal Simek <monstr@monstr.eu> wrote:
>
> Microblaze patches for 6.2-rc1
>
> - Cleanup PCI support

That tag looks normal in the email, but it's actually nastily encoded.
When I fetched it, I did this:

     git cat-file tag FETCH_HEAD | hexdump -c

and it shows

...
0000080   9   3   5   4   6       +   0   1   0   0  \n  \n   M   i   c
0000090   r   o   b   l   a   z   e 302 240   p   a   t   c   h   e   s
00000a0 302 240   f   o   r 302 240   6   .   2   -   r   c   1  \n  \n
00000b0   -       C   l   e   a   n   u   p       P   C   I       s   u
00000c0   p   p   o   r   t  \n   -   -   -   -   -   B   E   G   I   N
...

Note how the "spaces" between "Microblaze", "patches", "for" and "6.2"
are not actually regular space characters, but \xc2\a0, which is utf-8
encoding for unicode character A0 ("no-break space").

Please don't do that.  I have my editor show odd characters as hex
codes (I don't want any hidden information), which is why I noticed,
and I'm not sure why/how you did it.

               Linus

  reply	other threads:[~2022-12-12 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 10:07 [GIT PULL] arch/microblaze patches for 6.2-rc1 Michal Simek
2022-12-12 17:49 ` Linus Torvalds [this message]
2022-12-13  7:53   ` Michal Simek
2022-12-12 18:07 ` pr-tracker-bot

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='CAHk-=wiuqbgRZcotVf93Db4+gcPz8yAhW0mMfNZbEkM66rNB3Q@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    /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 NNTP newsgroup(s).