From: Sam James <sam@gentoo.org>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
Matt Jolly <Matt.Jolly@footclan.ninja>,
Brian Inglis <Brian.Inglis@Shaw.ca>,
Guillem Jover <guillem@hadrons.org>,
Tom Schwindl <schwindl@posteo.de>,
Marcos Fouces <marcos@debian.org>
Subject: Re: stdc: search function prototypes in ISO C documents
Date: Thu, 23 Mar 2023 05:35:47 +0000 [thread overview]
Message-ID: <87zg84vxjv.fsf@gentoo.org> (raw)
In-Reply-To: <ac2ba951-340f-d074-730b-ad8986338e8d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Alejandro Colomar <alx.manpages@gmail.com> writes:
> [[PGP Signed Part:Undecided]]
>
>
> On 3/22/23 20:49, Alejandro Colomar wrote:
>> Gidday!
>>
>> I created a git repository for the stdc(1) script, and created a signed
>> tag v0.1 for it.
>>
>> It's yet undocumented, but I plan to add a man page for it. Anyway,
>> being a bash(1) script, I guess it's quite readable to anyone here.
>>
>> Please suggest any improvements that you can think of =).
>
> Heh, of course I forgot to paste the link to the repo:
>
> cgit:
> <http://www.alejandro-colomar.es/src/alx/alx/doc/stdc.git/>
> git:
> <git://www.alejandro-colomar.es/src/alx/alx/doc/stdc.git>
Nice! I'm going to add this to my local ~/bin and play around
with it.
Thanks!
best,
sam
>
>>
>> Cheers,
>>
>> Alex
>>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2023-03-23 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 19:49 stdc: search function prototypes in ISO C documents Alejandro Colomar
2023-03-22 19:50 ` Alejandro Colomar
2023-03-23 5:35 ` Sam James [this message]
2023-03-23 0:41 ` Oskari Pirhonen
2023-03-23 13:05 ` 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=87zg84vxjv.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=Brian.Inglis@Shaw.ca \
--cc=Matt.Jolly@footclan.ninja \
--cc=alx.manpages@gmail.com \
--cc=guillem@hadrons.org \
--cc=linux-man@vger.kernel.org \
--cc=marcos@debian.org \
--cc=schwindl@posteo.de \
/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