From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Trial of replacing hyphens with en-dashes
Date: Sat, 13 Aug 2016 19:36:10 -0700 [thread overview]
Message-ID: <20160814023610.GG3482@linux.vnet.ibm.com> (raw)
In-Reply-To: <6ccb8aae-d3f1-9081-745c-a98ff8d2875c@gmail.com>
On Sat, Aug 13, 2016 at 12:38:11PM +0900, Akira Yokosawa wrote:
> >From a63dd50b648013af5780341f9c740bf9d9f6b65d Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Sat, 13 Aug 2016 11:17:19 +0900
> Subject: [RFC PATCH 0/3] Trial of replacing hyphens with en-dashes
>
> Hi Paul,
>
> This is an RFC patch series of my attempt to replace hyphens used for
> ranges of numbers with en-dashes.
> Instead of sending modifications in LaTeX sources as patches, I'm
> submitting scripts which do the replacements on the fly.
> The "sed" script is fairly stable now, and there is no false positives
> AFAIK.
> There might still be false negatives I'm not aware of. Any false positive
> would be addressed by adding a sed pattern.
> As a bonus, the sed pattern also contains fixes of typos such as "line~mm-nn".
>
> To try the replacement, at the top directory of perfbook, invoke the
> script by "sh utilities/dohyphen2endash.sh".
> You need to be in a clean git repository. This check is to ensure
> that you can revert the changes made by the script by "git reset --hard".
> So you might want to try this series on a test branch.
> Or the check of git status can be overridden by a "-f" or "--force" option.
>
> The modification by the scripts can be reviewed by "git diff" afterwards.
>
> It is up to the editor's choice whether or not to commit the result.
>
> Just adding the scripts to the repository is fine with me.
And, after inspecting the scripts, I took this approach.
Thank you!
Thanx, Paul
> Thanks, Akira
> ------
>
> Akira Yokosawa (3):
> Trial of replacing hyphens with en-dashes for number ranges
> dohyphen2endash.sh: Add check of git status
> dohyphen2endash.sh: Use mktemp to create temp file
>
> utilities/dohyphen2endash.sh | 74 ++++++++++++++++++++++++++++++++++++++++++++
> utilities/hyphen2endash.sh | 50 ++++++++++++++++++++++++++++++
> 2 files changed, 124 insertions(+)
> create mode 100644 utilities/dohyphen2endash.sh
> create mode 100644 utilities/hyphen2endash.sh
>
> --
> 1.9.1
>
prev parent reply other threads:[~2016-08-14 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 3:38 [RFC PATCH 0/3] Trial of replacing hyphens with en-dashes Akira Yokosawa
2016-08-13 3:39 ` [RFC PATCH 1/3] Trial of replacing hyphens with en-dashes for number Akira Yokosawa
2016-08-13 3:40 ` [RFC PATCH 2/3] dohyphen2endash.sh: Add check of git status Akira Yokosawa
2016-08-13 3:41 ` [RFC PATCH 3/3] dohyphen2endash.sh: Use mktemp to create temp file Akira Yokosawa
2016-08-14 2:36 ` Paul E. McKenney [this message]
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=20160814023610.GG3482@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox