[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72m8xAHGwEmTULqvfRzXe+dD7bx3_ALVOsU82_H3GDZdiQ@mail.gmail.com>
Date: Tue, 13 Dec 2022 12:25:55 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: ojeda@...nel.org, Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Rust for 6.2
On Tue, Dec 13, 2022 at 2:18 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Heh. You have an unusual habit of using the back-tick instead of the
> regular single quote character. It's not wrong, just surprising. I
> ended up just replacing it with the regular single quote.
As Nick pointed out, it is indeed Markdown. Rust code uses it e.g. for
function docs, so we use it for commit messages too and so on, which
makes it nice to copy-paste content from one part to the other etc.
When I wrote the tag message, I wondered whether to use the single
quotes, since I knew you keep consistent merge messages, but didn't
know if that included editing quotes. Thus I decided to just give it a
go and see what you edited or not for the next time.
> Maybe I'm biased against it, because I grew up with it being a dead
> key, and while my current keyboard has it very easily accessible, in
> many situations it's actually very inconvenient (ie it ends up being a
> dead key to generate acute grave on many European keyboard layouts).
Yeah, I share that pain in the usual Spanish layout... Until Markdown
started to become popular, I never used that key.
Since it is essentially a "normalized" plain text format (i.e. close
to what one would write anyway), I started using it for my notes at
some point given the growing support in text editors and websites, and
eventually in my emails too.
Cheers,
Miguel
Powered by blists - more mailing lists