git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Tokarev <annulen@yandex.ru>
To: Elijah Newren <newren@gmail.com>
Cc: Mike Castle <dalgoda@gmail.com>, Tao Klerks <tao@klerks.biz>,
	git <git@vger.kernel.org>
Subject: Re: Is --minimal ever not the right thing?
Date: Tue, 19 Dec 2023 21:09:49 +0300	[thread overview]
Message-ID: <20231219210949.747ddd50@RedEyes> (raw)
In-Reply-To: <CABPp-BEmgOAj17DozyXNaf-9CawDic4uTpMbckef3+zHf7URqQ@mail.gmail.com>

On Tue, 19 Dec 2023 09:55:34 -0800
Elijah Newren <newren@gmail.com> wrote:

> minimal is guaranteed to produce a minimal diff, i.e. fewest total
> subtractions and additions.  That is sometimes "best" quality, but
> definitely not always. 

I second this. Recently I had a case when I had to use --anchored
option of git diff to produce more informative diff instead of minimal
one.

      reply	other threads:[~2023-12-19 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 16:10 Is --minimal ever not the right thing? Tao Klerks
2023-12-19 17:25 ` Mike Castle
2023-12-19 17:55   ` Elijah Newren
2023-12-19 18:09     ` Konstantin Tokarev [this message]

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=20231219210949.747ddd50@RedEyes \
    --to=annulen@yandex.ru \
    --cc=dalgoda@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=tao@klerks.biz \
    /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).