From: Thomas Graf <tgraf@suug.ch>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: lib: rhashtable - Remove weird non-ASCII characters from comments
Date: Thu, 13 Nov 2014 07:54:02 +0000 [thread overview]
Message-ID: <20141113075402.GL19157@casper.infradead.org> (raw)
In-Reply-To: <20141113051048.GA1801@gondor.apana.org.au>
On 11/13/14 at 01:10pm, Herbert Xu wrote:
> My editor spewed garbage that looked like memory corruption on
> my screen. It turns out that a number of occurences of "fi" got
> turned into a ligature.
>
> This patch replaces these ligatures with the ASCII letters "fi".
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Fun ;-) These are the comments I copied from the PDF whitepaper.
Acked-by: Thomas Graf <tgraf@suug.ch>
next prev parent reply other threads:[~2014-11-13 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 5:10 lib: rhashtable - Remove weird non-ASCII characters from comments Herbert Xu
2014-11-13 7:54 ` Thomas Graf [this message]
2014-11-13 19:39 ` David Miller
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=20141113075402.GL19157@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox