public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Dmitry V. Levin" <ldv@strace.io>
Cc: Marco Cavenati <Marco.Cavenati@eurecom.fr>, linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info
Date: Tue, 10 Feb 2026 22:52:44 +0100	[thread overview]
Message-ID: <aYuneXoqJ_VPCFbw@devuan> (raw)
In-Reply-To: <20260210214145.GA1335@strace.io>

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

On 2026-02-10T23:41:45+0200, Dmitry V. Levin wrote:
> On Tue, Feb 10, 2026 at 10:20:02PM +0100, Alejandro Colomar wrote:
> > Hi Dmitry,
> > 
> > On 2026-02-10T22:53:47+0200, Dmitry V. Levin wrote:
> > > > > Looks good, thanks!
> > > > 
> > > > Should I take that as a Reviewed-by?
> > > 
> > > Feel free to add:
> > > 
> > > Reviewed-by: Dmitry V. Levin <ldv@strace.io>
> > 
> > Thanks!  I'll quote it, if you don't mind, as name-addreess pairs can't
> > contain an unquoted '.' --git(1) misbehaves on the '.', unless they
> > fixed it recently--.
> > 
> > 	Reviewed-by: "Dmitry V. Levin" <ldv@strace.io>
> > 
> > Is that okay?
> 
> I've been using the unquoted format for a while, but the quoted one
> is fine as well.

I've tried to reproduce it now, and they seem to have fixed it.  When
the patch is read by git-send-email(1) and it gets the addresses from
the trailer of the patch, it previously would have transformed
	Dmitry V. Levin <ldv@strace.io>
into
	Dmitry V.  Levin <ldv@strace.io>
Some depdenency (a library) of git(1) interpreted the '.' as ending
a sentence.  I've tried now, and it transforms
	Dmitry V. Levin <ldv@strace.io>
into
	"Dmitry V. Levin" <ldv@strace.io>
thus doing the right thing.  However, I expect some software might still
misbehave.  I remember having reproduced the bug not so long ago (maybe
one year?).


Cheers,
Alex

> 
> Thanks,
> 
> 
> -- 
> ldv
> 

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

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

  reply	other threads:[~2026-02-10 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 15:55 [PATCH] man/man2/ptrace.2: Add PTRACE_SET_SYSCALL_INFO, update struct ptrace_syscall_info Marco Cavenati
2026-01-21 16:56 ` Dmitry V. Levin
2026-02-10 20:14   ` Alejandro Colomar
2026-02-10 20:53     ` Dmitry V. Levin
2026-02-10 21:20       ` Alejandro Colomar
2026-02-10 21:41         ` Dmitry V. Levin
2026-02-10 21:52           ` Alejandro Colomar [this message]
2026-02-07 11:59 ` Marco Cavenati
2026-02-07 18:24   ` Alejandro Colomar
2026-02-07 18:38     ` Marco Cavenati

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=aYuneXoqJ_VPCFbw@devuan \
    --to=alx@kernel.org \
    --cc=Marco.Cavenati@eurecom.fr \
    --cc=ldv@strace.io \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox