tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4: ty: User-flow regression
Date: Fri, 10 Oct 2025 09:03:24 +0100	[thread overview]
Message-ID: <20251010080324.GC2988639@google.com> (raw)
In-Reply-To: <20251009-remarkable-charming-pogona-fd7a8f@lemur>

On Thu, 09 Oct 2025, Konstantin Ryabitsev wrote:

> On Thu, Oct 09, 2025 at 04:13:49PM +0100, Lee Jones wrote:
> > The that I'm highlighting occurs when changes have to be made to the

issue  ^

> > commit message.  My assumption is that the hash no longer matches and we
> > get:
> > 
> >  Auto-thankanating commits in for-mfd-next
> >  Found 5 of your commits since 1.day
> >  Calculating patch hashes, may take a moment...
> >  Nothing to do
> > 
> > Doh!  There should be something to do.
> 
> Curious, have you set your diff.algorithm anywhere in your git config to
> something like "patience" or "histogram"?

Not that I'm aware of:

  $ git config --get diff.algorithm
  <no output>

  $ git config --list | grep diff
  diff.wserrorhighlight=all
  diff.colormoved=zebra
  merge.conflictstyle=diff3

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-10-10  8:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 15:13 b4: ty: User-flow regression Lee Jones
2025-10-09 22:09 ` Konstantin Ryabitsev
2025-10-10  8:03   ` Lee Jones [this message]
2025-10-10 14:23     ` Konstantin Ryabitsev
2025-10-10 14:34       ` Lee Jones
2025-10-10 14:37         ` Konstantin Ryabitsev
2025-10-10 14:48           ` Lee Jones
2025-10-11 10:34           ` Greg KH
2025-10-21 10:56             ` Lee Jones
2025-10-21 11:25               ` Vlastimil Babka (SUSE)
2025-10-21 14:38                 ` Lee Jones

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=20251010080324.GC2988639@google.com \
    --to=lee@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@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;
as well as URLs for NNTP newsgroup(s).