git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Tiago de Bem Natel de Moura <t.nateldemoura@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git diff-tree do not honor diff.orderfile config
Date: Fri, 5 Jul 2024 17:04:44 -0400	[thread overview]
Message-ID: <Zohf7LzaRHaG9vX6@nand.local> (raw)
In-Reply-To: <CAJFVNCfz_-Dvd0ctc4w-2jsthyPFxy=HOutj=3PbNnQ-Gsz84A@mail.gmail.com>

On Fri, Jul 05, 2024 at 11:28:23AM +0100, Tiago de Bem Natel de Moura wrote:
> What did you do before the bug happened? (Steps to reproduce your issue)
> The config `diff.orderfile` is not being honored in the `git diff-tree` command
> as stated by the documentation.

Makes sense... the diff.orderFile configuration is part of the "UI" set
of diff.* configuration options, which are honored by porcelain commands
like commit, diff, log, etc., but not by plumbing commands like
diff-tree.

I think from 6d8940b562 (diff: add diff.orderfile configuration
variable, 2013-12-18) adding it to the UI-only configuration set was
intentional, but it is somewhat awkward that we respect -O but not the
configuration it falls back on.

So I suppose the question is whether supporting -O from diff-tree is
sensible. If it is, then reading the diff.orderFile configuration option
is a no-brainer. But if it isn't, then we should probably not make a bad
situation worse by adding support for it.

Thanks,
Taylor

  reply	other threads:[~2024-07-05 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 10:28 git diff-tree do not honor diff.orderfile config Tiago de Bem Natel de Moura
2024-07-05 21:04 ` Taylor Blau [this message]
2024-07-06  7:02   ` Jeff King
2024-07-06 22:10   ` Junio C Hamano
2024-07-08 12:49     ` Tiago de Bem Natel de Moura
2024-07-06  7:38 ` Junio C Hamano

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=Zohf7LzaRHaG9vX6@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=t.nateldemoura@gmail.com \
    /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).