From: Johannes Weiner <jweiner@redhat.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
liwp.linux@gmail.com, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org,
Wanpeng Li <liwp@linux.vnet.ibm.com>
Subject: Re: [PATCH] unmapped quotes
Date: Sat, 12 May 2012 16:09:18 +0200 [thread overview]
Message-ID: <20120512140918.GA1407@redhat.com> (raw)
In-Reply-To: <20120512112637.GA11577@localhost>
On Sat, May 12, 2012 at 07:26:37PM +0800, Fengguang Wu wrote:
> On Sat, May 12, 2012 at 01:02:36PM +0400, Michael Tokarev wrote:
> > On 12.05.2012 12:47, liwp.linux@gmail.com wrote:
> > > - * If we're over `background_thresh' then the writeback threads are woken to
> > > + * If we're over 'background_thresh' then the writeback threads are woken to
> >
> > I can't say the original is wrong. Since these quotes don't have
> > "open" and "close" versions like {} or () pairs does, people often
> > use ` as opening and ' as closing - while staying within ascii.
> > Alternatives are things like « » or other things, but these aren't
> > ascii anymore. So I'd say keep it alone... ;)
>
> Agreed. For example, latex uses ` and ' as opening and closing pairs.
> That does look a bit weird for C and shell users ;)
In some fonts, ` is actually symmetrical to '.
If you change it to 'background_thresh', it will look like crap in my
Sütterlin emacs.
next prev parent reply other threads:[~2012-05-12 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 8:47 [PATCH] unmapped quotes liwp.linux
2012-05-12 9:02 ` Michael Tokarev
2012-05-12 11:26 ` Fengguang Wu
2012-05-12 14:09 ` Johannes Weiner [this message]
2012-05-13 2:18 ` Cong Wang
2012-05-12 14:32 ` Bernd Petrovitsch
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=20120512140918.GA1407@redhat.com \
--to=jweiner@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=liwp.linux@gmail.com \
--cc=liwp@linux.vnet.ibm.com \
--cc=mjt@tls.msk.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.