From: Edward Cree <ecree.xilinx@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: alsa-devel@alsa-project.org, kvm@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-iio@vger.kernel.org, linux-pci@vger.kernel.org,
linux-fpga@vger.kernel.org, dri-devel@lists.freedesktop.org,
keyrings@vger.kernel.org, linux-riscv@lists.infradead.org,
Jonathan Corbet <corbet@lwn.net>,
linux-rdma@vger.kernel.org, x86@kernel.org,
linux-acpi@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-input@vger.kernel.org, linux-ext4@vger.kernel.org,
intel-gfx@lists.freedesktop.org, linux-media@vger.kernel.org,
linux-pm@vger.kernel.org, linux-sgx@vger.kernel.org,
coresight@lists.linaro.org, rcu@vger.kernel.org,
mjpeg-users@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org,
linux-hwmon@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-integrity@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [f2fs-dev] [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII
Date: Mon, 10 May 2021 14:58:59 +0100 [thread overview]
Message-ID: <b3366f65-35e1-8f1a-d8d8-ebd444c9499d@gmail.com> (raw)
In-Reply-To: <20210510153807.4405695e@coco.lan>
On 10/05/2021 14:38, Mauro Carvalho Chehab wrote:
> Em Mon, 10 May 2021 14:16:16 +0100
> Edward Cree <ecree.xilinx@gmail.com> escreveu:
>> But what kinds of things with × or — in are going to be grept for?
>
> Actually, on almost all places, those aren't used inside math formulae, but
> instead, they describe video some resolutions:
Ehh, those are also proper uses of ×. It's still a multiplication,
after all.
> it is a way more likely that, if someone wants to grep, they would be
> doing something like this, in order to get video resolutions:
Why would someone be grepping for "all video resolutions mentioned in
the documentation"? That seems contrived to me.
-ed
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-05-10 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 10:26 [f2fs-dev] [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII Mauro Carvalho Chehab
2021-05-10 10:26 ` [f2fs-dev] [PATCH 27/53] docs: filesystems: f2fs.rst: avoid using UTF-8 chars Mauro Carvalho Chehab
2021-05-11 3:16 ` Chao Yu
2021-05-10 10:52 ` [f2fs-dev] [PATCH 00/53] Get rid of UTF-8 chars that can be mapped as ASCII Thorsten Leemhuis
2021-05-10 11:19 ` Mauro Carvalho Chehab
2021-05-10 12:27 ` Mauro Carvalho Chehab
[not found] ` <2ae366fdff4bd5910a2270823e8da70521c859af.camel@infradead.org>
2021-05-10 11:55 ` Mauro Carvalho Chehab
2021-05-10 12:29 ` beroal
2021-05-10 13:16 ` Edward Cree
2021-05-10 13:38 ` Mauro Carvalho Chehab
2021-05-10 13:58 ` Edward Cree [this message]
2021-05-10 13:59 ` Matthew Wilcox
2021-05-10 14:33 ` Edward Cree
2021-05-11 9:00 ` Mauro Carvalho Chehab
2021-05-10 14:00 ` Ben Boeckel
[not found] ` <de6d1fa5b7934f4afd61370d9c58502bef588466.camel@infradead.org>
2021-05-10 19:22 ` Theodore Ts'o
2021-05-11 9:37 ` Mauro Carvalho Chehab
2021-05-11 9:25 ` Mauro Carvalho Chehab
2021-05-10 21:57 ` Adam Borowski
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=b3366f65-35e1-8f1a-d8d8-ebd444c9499d@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwmw2@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=keyrings@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mjpeg-users@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).