public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 19 Dec 2022 20:10:25 +0100	[thread overview]
Message-ID: <acebbd20-d235-7668-5481-2f043cb2c9cb@gmail.com> (raw)
In-Reply-To: <20221219165900.dfgjj5spciy4cqlt@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 2328 bytes --]

Hi Branden,

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...

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 :)

> 
> Yes, I'll do it.  Maybe today, maybe later this week.

Sure.  I don't think we can say this is an RC bug 22 years after the page was 
last updated in actual content (rather than minor updates from Michael, mostly 
as part of global fixes).

> 
>> I have a patch for an extension that wasn't covered by this file.  I'm
>> guessing pkg-config wasn't invented when this page was written?
>> That's really old...  It seems the page goes back to man-pages 1.0
>> (with some additions later; mostly in 1.21).
> 
> The last person credited as changing it in the file itself, as you no
> doubt saw,

Actually, I didn't.  I'm so used to git log, that I usually forget to check page 
headers.  Especially now that I have access to the entire history (no authors, 
but at least versions and times).

BTW, I agree with you that the reversed history is a bit weird and confusing.  I 
thought of a new method that would connect both histories while keeping a 
forward history:

A separate orphan branch in normal order, starting at 1.0, which ends at 1.70. 
And then git allows merging orphan branches, so I can create a merge commit 
between both 1.70 commits, which of course is a no-op, but one that tells git 
where and how these branches join.

> was David Wheeler (no, the other one)

Didn't know of the other David Wheeler.

> in 2000.  I think that
> does antedate pkg-config.

According to wikipedia, pkg-config(1)'s initial release is also from 2000.  So, 
yes, probably it wasn't widely known at the time.

> 
> Regards,
> Branden

Cheers,

Alex

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

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

  reply	other threads:[~2022-12-19 19:11 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 [this message]
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
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=acebbd20-d235-7668-5481-2f043cb2c9cb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox