From: Alejandro Colomar <alx@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 1/4] man/man3*: document the glibc 2.42+ baud_t termios interface
Date: Tue, 30 Jun 2026 23:19:15 +0200 [thread overview]
Message-ID: <akQydQ9Qa2TOvW2p@devuan> (raw)
In-Reply-To: <edef56f0-90d6-47a6-8a4d-314825f3167b@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Hi,
On 2026-06-30T13:41:16-0700, H. Peter Anvin wrote:
> On 2026-06-30 03:39, Alejandro Colomar wrote:
> >
> > Hmmm, even with --diff-algorithm=patience it shows the diff too badly.
> > I've been trying, and --diff-algorithm=histogram shows a much nicer
> > diff. I have the following in my gitconfig:
> >
> > [diff]
> > algorithm = histogram
> >
> > I suggest adding that to your gitconfig file. It is implicitly also
> > used when you generate patches. The histogram algorithm works quite
> > nicely (I've been using for a few years already).
> >
> OK, I'll try that. I haven't played with the diff algorithms, perhaps because
> I naïvely assumed that the default would be the "currently best" algorithm and
The default is the fastest (I believe), but it's actually bad. While
there are a few weird cases where the histogram algorithm fails badly,
it regularly results in better diffs. :)
> ending up using a stale algorithm choice when a new one is introduced is
> unfortunate.
TBH, I don't know why they didn't change the default.
Cheers,
Alex
>
> -hpa
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-30 21:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:02 [PATCH 1/1] man/man3*: document the glibc 2.42+ baud_t termios interface H. Peter Anvin
2026-06-29 9:51 ` Alejandro Colomar
2026-06-29 13:59 ` [PATCH v2 0/4] update termios(3) for glibc 2.42+ and POSIX.1-2024 H. Peter Anvin
2026-06-29 13:59 ` [PATCH v2 1/4] man/man3*: document the glibc 2.42+ baud_t termios interface H. Peter Anvin
2026-06-30 10:39 ` Alejandro Colomar
2026-06-30 20:37 ` H. Peter Anvin
2026-06-30 21:17 ` Alejandro Colomar
2026-06-30 22:01 ` H. Peter Anvin
2026-07-01 14:53 ` Alejandro Colomar
2026-06-30 22:50 ` G. Branden Robinson
2026-06-30 20:41 ` H. Peter Anvin
2026-06-30 21:19 ` Alejandro Colomar [this message]
2026-06-29 13:59 ` [PATCH v2 2/4] man/man3/termios.3: note that setserial(8) rate hacking is dangerous H. Peter Anvin
2026-06-30 9:15 ` Alejandro Colomar
2026-06-29 13:59 ` [PATCH v2 3/4] man/man3/termios.3: document that output baud rate has priority H. Peter Anvin
2026-06-29 13:59 ` [PATCH v2 4/4] man/man3/termios.3: document that cfsetispeed(..., 0) is deprecated H. Peter Anvin
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=akQydQ9Qa2TOvW2p@devuan \
--to=alx@kernel.org \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--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