From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH 0/3] Get rid of plain dashes for ranges
Date: Fri, 6 Dec 2019 00:14:30 +0900 [thread overview]
Message-ID: <abbbd715-64b5-e210-240a-e18680f4e1ea@gmail.com> (raw)
Hi Paul,
In your recent updates, I see you have used endashes for range
of numbers.
So I think it is high time to get rid of other plain dashes used
for ranges. After the change made in commit 38eec3194c9a
("Use \crefrange{}{} for range of figures"), there remain around
twenty such plain dashes.
Patch #1 updates a case under bib/.
Patch #2 takes care of other plain dashes.
Patch #3 updates the section "En Dash" in style guide. It also adds
a section on cross-reference.
Please permit the brevity of change logs in this set.
Thanks, Akira
--
Akira Yokosawa (3):
bib/hw.bib: Use endash for volume range
treewide: Use endash for ranges
styleguide: Update on cross-reference and endash
advsync/rt.tex | 2 +-
appendix/styleguide/styleguide.tex | 92 ++++++++++++++++++++++------
appendix/toyrcu/toyrcu.tex | 2 +-
appendix/whymb/whymemorybarriers.tex | 2 +-
bib/hw.bib | 2 +-
cpu/overheads.tex | 2 +-
datastruct/datastruct.tex | 6 +-
defer/hazptr.tex | 2 +-
easy/easy.tex | 2 +-
future/formalregress.tex | 2 +-
legal.tex | 2 +-
locking/locking.tex | 4 +-
12 files changed, 87 insertions(+), 33 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-05 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:14 Akira Yokosawa [this message]
2019-12-05 15:15 ` [PATCH 1/3] bib/hw.bib: Use endash for volume range Akira Yokosawa
2019-12-05 15:17 ` [PATCH 2/3] treewide: Use endash for ranges Akira Yokosawa
2019-12-05 15:19 ` [PATCH 3/3] styleguide: Update on cross-reference and endash Akira Yokosawa
2019-12-05 16:50 ` [PATCH 0/3] Get rid of plain dashes for ranges Paul E. McKenney
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=abbbd715-64b5-e210-240a-e18680f4e1ea@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@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 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.