linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Zach OKeefe <zokeefe@google.com>, Yang Shi <shy828301@gmail.com>,
	linux-mm@kvack.org, linux-man@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH man-pages v3 4/4] madvise.2: add documentation for MADV_COLLAPSE
Date: Mon, 31 Oct 2022 20:51:10 -0500	[thread overview]
Message-ID: <20221101015110.jjavjoltbwc3ohep@illithid> (raw)
In-Reply-To: <bb3b5c3c-3966-ea1a-6d84-4f7f3afa37ca@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

At 2022-10-31T22:15:09+0100, Alejandro Colomar wrote:
> The issue was in line 474, and the issue is that it uses a weird single
> quote. Please use the foillowing ASCII character for the single quote (see
> ascii(7)):
> 047   39    27    '
[...]
> I'll report a bug to groff(1) about the issue with the line count.

Thanks, Alex.  There appear to be some very old bugs around input line
number tracking in GNU eqn, possibly going back 30+ years.

I've committed a regression test[1] and fix.[2]  The fix can be expected
(along with literally hundreds of others) in groff 1.23.

And now I see I managed to sneak a cosmetic indentation error into the
commit message for the second (but not the ChangeLog), where I'm stuck
with it forever.  Oh well.

Regards,
Branden

[1] https://git.savannah.gnu.org/cgit/groff.git/commit/?id=7e23e1342077a6d7c0b02c3d666f131d95f2b510
[2] https://git.savannah.gnu.org/cgit/groff.git/commit/?id=dc98a8b09e7f3dcfe968b978eb210f468db78cc9

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-01  1:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 22:32 [PATCH man-pages v3 0/4] Add MADV_COLLAPSE documentation Zach OKeefe
2022-10-21 22:32 ` [PATCH man-pages v3 1/4] madvise.2: update THP file/shmem documentation for +5.4 Zach OKeefe
2022-10-30 11:41   ` Alejandro Colomar
2022-10-31 16:33     ` Zach O'Keefe
2022-10-31 20:11       ` Alejandro Colomar
2022-10-21 22:32 ` [PATCH man-pages v3 2/4] madvise.2: document reliable probe for advice support Zach OKeefe
2022-10-30 11:44   ` Alejandro Colomar
2022-10-31 16:33     ` Zach O'Keefe
2022-10-31 20:21       ` Alejandro Colomar
2022-10-31 21:24         ` Zach O'Keefe
2022-10-21 22:32 ` [PATCH man-pages v3 3/4] process_madvise.2: fix capability and ptrace requirements Zach OKeefe
2022-10-30 11:50   ` Alejandro Colomar
2022-10-31 19:13     ` Suren Baghdasaryan
2022-10-31 20:24       ` Alejandro Colomar
2022-10-31 21:25         ` Zach O'Keefe
2022-10-21 22:33 ` [PATCH man-pages v3 4/4] madvise.2: add documentation for MADV_COLLAPSE Zach OKeefe
2022-10-31 21:15   ` Alejandro Colomar
2022-10-31 23:00     ` Zach O'Keefe
2022-11-01  1:51     ` G. Branden Robinson [this message]
2022-11-01 12:12       ` Alejandro Colomar
2022-12-11 17:59   ` Alejandro Colomar
2022-12-11 21:51     ` Zach O'Keefe
2022-12-11 21:55       ` Alejandro Colomar
2022-12-11 22:37         ` Zach O'Keefe
2022-12-11 22:39           ` Alejandro Colomar

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=20221101015110.jjavjoltbwc3ohep@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtk.manpages@gmail.com \
    --cc=shy828301@gmail.com \
    --cc=zokeefe@google.com \
    /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