Re: [PATCH v1 08/11] man/man3type/stat.3type: HISTORY: Specify first POSIX appearance of st_{rdev,blksize,blocks}

[Alejandro Colomar <alx@kernel.org>]

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

Hi Seth,

On Sat, Jan 10, 2026 at 06:00:14AM +0000, Seth McDonald wrote:
> On Friday, 9 January 2026 at 20:00, Alejandro Colomar <alx@kernel.org> wrote:
> > Hi Seth,
> [...]
> > You may be interested in diffman-git(1). I think it would help
> > reviewing your diffs. Here's some example of how it works:
> [...]
> > For more documentation, see diffman-git(1), of course. :)
> 
> That does look quite useful!  I've seen it used before in the mailing
> list, but couldn't initially find its documentation.  Which I now
> realise is because I was looking for its man page in my installed man
> pages, rather than in the repository *for this documentation* (ironic,
> I know).

Yup, I wrote that script very recently.  Distros have not packaged it
yet.

> > It's provided in the repository, in case your distro doesn't provide it
> > yet. You can install it with the usual
> >
> > $ make -R -j4 && sudo make -R -j4 install;
> >
> > Or just run it from the repo, since it's a bash(1) script. It's here:
> >
> > $ find * | grep diffman-git
> > man/man1/diffman-git.1
> > src/bin/diffman-git
> 
> My distro (Debian 13) indeed doesn't seem to provide it yet, so I've
> installed it successfully via the repo.

The only distro that already provides the scripts from this repo, AFAIR,
is Arch.  I've been talking to Fedora and Debian, and they'll likely
package them soon.

> I'm glad it's a bash script,
> as I'd be a little more hesitant to install a binary executable.

Yup.

> [...]
> > I have a question: do you use mutt(1) or neomutt(1) by chance?
> 
> Currently neither; I generally just use the Proton Mail Linux app.
> Mainly because it's a familiar interface from before I switched to Linux
> in mid-2025.

I was mentioning it because since you send many patches, it would be
interesting if you could sign them with gpg(1).  It's not necessary, but
if you used one of these, it would be trivial to sign them.

> However, I have been really getting into TUIs recently.

Nice!  :-)

> So if you recommend either, then I'd be enthusiastic to give it a try.

I recommend both.  Personally I like mutt(1) because it's simpler, but
for sending patches, neomutt(1) is useful because it allows signing
patches cryptographically with gpg(1) in batch mode (called by
git-send-email(1)).  mutt(1) can only sign emails in interactive mode.

I certainly recommend you give a try to mutt(1) first.  For interactive
use, I don't need more than that.  I learnt to use it with this youtube
video: <https://www.youtube.com/watch?v=2jMInHnpNfQ>.  If you want more
help, I can share my configuration files with you, and maybe clarify
some doubts.

neomutt(1) is a fork of mutt(1) with (many) more features, but I prefer
simpler software with less features.


Have a lovely day!
Alex

> ----
> Seth McDonald.
> sethmcmail at pm dot me (mailing lists)
> 2336 E8D2 FEB1 5300 692C  62A9 5839 6AD8 9243 D369




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

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