git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: pb/range-diff-with-submodule (was: Re: What's cooking in git.git (Jun 2022, #03; Fri, 10))
Date: Sat, 11 Jun 2022 11:08:47 -0400	[thread overview]
Message-ID: <6fc6c301-591f-7e51-f9c2-ee74f9428664@gmail.com> (raw)
In-Reply-To: <xmqqsfobc1hw.fsf@gitster.g>

Hi Junio,

Le 2022-06-10 à 23:39, Junio C Hamano a écrit :

> --------------------------------------------------
> [Cooking]
> 
> * pb/range-diff-with-submodule (2022-06-06) 1 commit
>   (merged to 'next' on 2022-06-07 at e5e31590c4)
>  + range-diff: show submodule changes irrespective of diff.submodule
> 
>  "git range-diff" did not show anything for submodules that changed
>  in the ranges being compared.  Change the behaviour to include the
>  "--submodule=short" output unconditionally to be compared.
> 
>  Will merge to 'master'.
>  source: <pull.1244.v2.git.1654549153769.gitgitgadget@gmail.com>
> 

As I wrote in my reply to your previous "what's cooking" [1], I think
the merge message (and thus release notes blurb) for this topic could 
be a little more precise, something like:


"git -c diff.submodule=log range-diff" did not show anything for 
submodules that changed in the ranges being compared, and 
"git -c diff.submodule=diff range-diff" did not work correctly.
Fix this by including the "--submodule=short" output 
unconditionally to be compared.


I was not sure if you disagreed and thus did not answer on Tuesday,
or if my reply fell through the cracks, so I'm trying again.

Cheers,

Philippe.


[1] https://lore.kernel.org/git/15dd34af-14c1-5b41-5d33-a2e3b9611c25@gmail.com/

  reply	other threads:[~2022-06-11 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  3:39 What's cooking in git.git (Jun 2022, #03; Fri, 10) Junio C Hamano
2022-06-11 15:08 ` Philippe Blain [this message]
2022-06-13 15:01 ` ds/branch-checked-out (was Re: What's cooking in git.git (Jun 2022, #03; Fri, 10)) Derrick Stolee

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=6fc6c301-591f-7e51-f9c2-ee74f9428664@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).