[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiuqbgRZcotVf93Db4+gcPz8yAhW0mMfNZbEkM66rNB3Q@mail.gmail.com>
Date: Mon, 12 Dec 2022 09:49:18 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Michal Simek <monstr@...str.eu>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze patches for 6.2-rc1
On Thu, Dec 8, 2022 at 2:07 AM Michal Simek <monstr@...str.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
Powered by blists - more mailing lists