All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 3/3] man2/syscalls.2: srcfix
Date: Sat, 27 Apr 2024 00:12:48 +0200	[thread overview]
Message-ID: <Ziwm4MlaUT7LNjFt@debian> (raw)
In-Reply-To: <20240426214102.6pioaplkwkbch6iw@illithid>

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

Hi Branden,

On Fri, Apr 26, 2024 at 04:41:02PM -0500, G. Branden Robinson wrote:
> The intermediate steps are not useful.  For example, after the first sed
> script, we have changes like this:
> 
> diff --git a/man2/syscalls.2 b/man2/syscalls.2
> index 7a7d6d730..979dba538 100644
> --- a/man2/syscalls.2
> +++ b/man2/syscalls.2
> @@ -187,7 +187,8 @@ .SS System call list
>  \fBchdir\fP(2)	1.0
>  \fBchmod\fP(2)	1.0
>  \fBchown\fP(2)	2.2	T{
> -See \fBchown\fP(2) for
> +See .BR chown (2)
> +for
>  version details
>  T}
>  \fBchown32\fP(2)	2.4
> 
> Having ".BR chown (2)" sitting out there as unformatted text (because
> macro calls have to _start_ an input line) is obviously not useful.
> 
> However, I did discover that the second script was a no-op!  So I'm
> dropping that (actually, replacing it) and will submit a v2.

Good.  :-)

Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es/>

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

      reply	other threads:[~2024-04-26 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 22:39 [PATCH 3/3] man2/syscalls.2: srcfix G. Branden Robinson
2024-04-17 10:10 ` Alejandro Colomar
2024-04-26 21:41   ` G. Branden Robinson
2024-04-26 22:12     ` Alejandro Colomar [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=Ziwm4MlaUT7LNjFt@debian \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@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.