public inbox for linux-man@vger.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, bug-gnulib@gnu.org
Subject: Re: [PATCH v1 1/1] man/man3/strnul.3: New page
Date: Sat, 21 Feb 2026 21:55:01 +0100	[thread overview]
Message-ID: <aZobaC_UCI7CYkcZ@devuan> (raw)
In-Reply-To: <20260221200509.vxfbyyg7v2d2svhb@illithid>

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

Hi Branden,

On 2026-02-21T14:05:09-0600, G. Branden Robinson wrote:
> > > I assume that the string library reforms you're pursuing are
> > > intended in part to be adopted by newcomers to C.
> > 
> > I intend old programmers to use it too.
> 
> Goooooood luck.  As we've seen, to take gets(3) away from some people
> has required killing it off from the standard C library itself.
> 
> Some old programmers get really good.  Some just get old.
> 
> > I guess you're expecting a patch to groff once this is in a branch of
> > gnulib you're using.  ;)
> 
> No, not expecting.  :)

Well, now you know.  :)

> 
> Replacing our bespoke `strsave()` with `strdup()` seems like a higher
> priority to me.

Will you, or should I?

> 
> https://savannah.gnu.org/bugs/?66518
> 
> Regards,
> Branden

Cheers,
Alex

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

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

  reply	other threads:[~2026-02-21 20:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-21 15:02 [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:02 ` [PATCH v1 1/1] man/man3/strnul.3: New page Alejandro Colomar
2026-02-21 17:41   ` G. Branden Robinson
2026-02-21 19:56     ` Alejandro Colomar
2026-02-21 20:02       ` Simon Josefsson
2026-02-21 20:45         ` Alejandro Colomar
2026-02-21 20:05       ` G. Branden Robinson
2026-02-21 20:55         ` Alejandro Colomar [this message]
2026-02-22  1:48   ` Paul Eggert
2026-02-22 11:21     ` Alejandro Colomar
2026-02-22 13:46       ` Alejandro Colomar
2026-02-22 14:10         ` Bruno Haible
2026-02-22 14:19           ` Alejandro Colomar
2026-02-22 14:21             ` Alejandro Colomar
2026-02-21 15:04 ` [PATCH v1 0/1] Document strnul(3) Alejandro Colomar
2026-02-21 15:09   ` Alejandro Colomar
2026-02-21 20:53 ` [PATCH v2 " Alejandro Colomar
2026-02-21 20:53   ` [PATCH v2 1/1] man/man3/strnul.3: New page 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=aZobaC_UCI7CYkcZ@devuan \
    --to=alx@kernel.org \
    --cc=bug-gnulib@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox