From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: patching suffixes(7) (was: groff 1.23.0.rc2 status report)
Date: Tue, 20 Dec 2022 11:12:16 +0100 [thread overview]
Message-ID: <88617ad8-bb2f-65f0-ea61-ecb0e9043147@gmail.com> (raw)
In-Reply-To: <20221220034059.piz7qsu3r67j2np3@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 4376 bytes --]
Hi Branden,
On 12/20/22 04:40, G. Branden Robinson wrote:
> At 2022-12-19T20:10:25+0100, Alejandro Colomar wrote:
>> On 12/19/22 17:59, G. Branden Robinson wrote:
>>> [dropping Deri and groff@]
>>>
>>> At 2022-12-19T17:39:37+0100, Alejandro Colomar wrote:
>>>> Would you mind sending a patch that I can apply with git? I could
>>>> manually edit the file you attached, but I'm feeling lazy for that
>>>> :\
>>>
>>> Damn. Our lazinesses are duelling. :P
>>
>> :P
>>
>> I actually wonder how producing such a diff was simpler than just
>> copying the output of git diff...
>
> I don't find "diff -u <tab-completion>{,.new}" very difficult.
>
> (I often do that in repos that I mostly read as opposed to contributing
> to; that way my half-baked ideas don't get in the way of a rebase pull.
> Branching doesn't solve that problem, and if I git-stash something in
> such a repo I'm likely to forget about it, or not think to check there.)
Hmmm, can make sense. (I branch for such occasions.) (stash && rebase-pull &&
stash-pop is also common, but that's for repos in which I work more often and
don't have to pull tons of changes.) :)
>
>> BTW, I still plan releasing man-pages-6.02 in a two days, and feel
>> confident enough about the string changes (modulo a few tweaks that
>> I'll apply) to ship them in it. If you have any comments about them,
>> please voice them :)
>
> I have weak preference for the name "string_copying(7)" over
> "string_copy(7)", but leaving the summary-description the same.
>
I prefer it too. string_copy was for when this page was going to substitute the
other ones, so I wanted it to have a name resembling them. But now I like
"copying" more. So, done, and pushed. A new page is born.
> Apart from that I have no comments, apart from encouraging you in your
> effort to reform common practice to something less sloppy.
Thanks :)
> I think you
> will get pushback from people who (1) don't appreciate how horrible the
> C string library is, in part because they have mazed themselves with the
> notion that the engineers at the Bell Labs CSRC were all infallible
> giants who deigned to walk among us mortals for a while; and (2) would
> rather wait until some total replacement solution comes along, which of
> course they would oppose with at least much passion.
>
> Nevertheless, once in a while they'll make good points. Take that
> opportunity to anneal the quality of your initiative.
>
> The standard I/O library is a disaster, too. Much more esteemed people
> than I have made this point, such as Korn and Vo, who presented their
> case at USENIX in 1991.[1] Of course, they did the smart thing back
> then and didn't FLOSS-license it, possibly under direction from AT&T
> management. Thanks to that shrewd advice, sfio.h stormed to success and
> ubiquity instead of being nearly forgotten.
That's why I went for public domain for the APIs and basic implementations, and
BSD-3-Clause for the string_copying(7) page. I'd like it to be as widespread as
possible.
However, my own library implementation is LGPL-3.0-or-later, as couldn't be
otherwise.
>
> But even a permissive license may well have not been enough. The
> average programmer will happily drink from a pool of dioxin as long as
> it is a familiar one. >
>>> was David Wheeler (no, the other one)
>>
>> Didn't know of the other David Wheeler.
>
> Well, David J. Wheeler (computer scientist) passed away in 2004, so
> possibly David A. Wheeler (computer scientist) gets mistaken for him
> less often now.
>
> I've been making this joke for years. It hasn't worked once. Like the
> average programmer, I learn nothing from this.
>
>> According to wikipedia, pkg-config(1)'s initial release is also from
>> 2000. So, yes, probably it wasn't widely known at the time.
>
> It was an innocent time, when packaging was still young and exciting,
I need to learn packaging some day. I should learn Debian packaging to package
this new library...
> and before JavaScript people getting paid a lot to work in e-commerce
> decided they could do it better than everyone else.
>
> Regards,
> Branden
>
> [1] https://www.cs.princeton.edu/courses/archive/fall97/cs595/sfio.ps
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-20 10:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220906191320.447t5awx3rcb5d5b@illithid>
[not found] ` <a7b8c6b3-a8e8-6ab7-6cf4-118446849a9c@gmail.com>
[not found] ` <dca0e251-7481-7f1e-4077-0ddee070a357@gmail.com>
[not found] ` <20220906204245.hzhq2s7yha6zzgrh@illithid>
[not found] ` <30e80fe0-f0ce-d6cd-ee40-28692e5a5f82@gmail.com>
[not found] ` <5c1e8620-e4ff-c79a-1d4e-11f797276726@gmail.com>
[not found] ` <20221116234049.GA1229865@if>
[not found] ` <f306a83a-306d-e3d0-5d25-bf07da3da59f@gmail.com>
2022-11-17 0:28 ` Chapters of the manual (was: Bug#1018737: /usr/bin/rst2man: rst2man: .TH 5th field shouldn't be empty) Alejandro Colomar
2022-12-11 16:40 ` Ping^1: " Alejandro Colomar
2022-12-11 19:05 ` Michael Haardt
2022-12-11 19:21 ` Alejandro Colomar
2022-12-11 21:10 ` Michael Haardt
2022-12-12 0:34 ` Douglas McIlroy
2022-12-12 11:39 ` Alejandro Colomar
2022-12-12 8:58 ` Ralph Corderoy
2022-12-12 13:19 ` G. Branden Robinson
2022-12-12 13:57 ` Andries E. Brouwer
2022-12-12 13:39 ` Colin Watson
2022-12-12 13:48 ` Alejandro Colomar
[not found] ` <1719285.QkHrqEjB74@pip>
[not found] ` <01989003-349f-fb6b-f460-89106b82bc34@gmail.com>
[not found] ` <2176657.1BCLMh4Saa@pip>
2022-12-17 11:51 ` Ping^1: " Alejandro Colomar
2022-12-17 13:19 ` [BUG] gropdf, tbl: Completely broken table (was: Ping^1: Chapters of the manual (was: Bug#1018737: ...)) Alejandro Colomar
2022-12-17 16:08 ` G. Branden Robinson
2022-12-17 21:26 ` Deri
2022-12-18 11:25 ` Alejandro Colomar
2022-12-18 5:49 ` [BUG] gropdf, tbl: Completely broken table Ralph Corderoy
2022-12-18 11:01 ` Alejandro Colomar
2022-12-18 11:46 ` [BUG] gropdf, tbl: Completely broken table (was: Ping^1: Chapters of the manual (was: Bug#1018737: ...)) Alejandro Colomar
2022-12-19 5:32 ` groff 1.23.0.rc2 status report (was: [BUG] gropdf, tbl: Completely broken table) G. Branden Robinson
2022-12-19 12:58 ` Deri
2022-12-19 16:39 ` Alejandro Colomar
2022-12-19 16:59 ` patching suffixes(7) (was: groff 1.23.0.rc2 status report) G. Branden Robinson
2022-12-19 19:10 ` Alejandro Colomar
2022-12-19 19:54 ` prehistory branch (was: patching suffixes(7) (was: groff 1.23.0.rc2 status report)) Alejandro Colomar
2022-12-19 20:05 ` Alejandro Colomar
2022-12-20 3:40 ` patching suffixes(7) (was: groff 1.23.0.rc2 status report) G. Branden Robinson
2022-12-20 10:12 ` Alejandro Colomar [this message]
2022-12-19 16:51 ` groff 1.23.0.rc2 status report (was: [BUG] gropdf, tbl: Completely broken table) G. Branden Robinson
2022-12-17 21:37 ` Ping^1: Chapters of the manual (was: Bug#1018737: /usr/bin/rst2man: rst2man: .TH 5th field shouldn't be empty) Deri
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=88617ad8-bb2f-65f0-ea61-ecb0e9043147@gmail.com \
--to=alx.manpages@gmail.com \
--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.