Re: [PATCH 00/26] git-log: implement new --diff-merge options
- From
Elijah Newren <newren@gmail.com>
- Date
- Dec 9, 2020, 03:31 UTC
- Message-ID
- <CABPp-BHWhiUZ=wCSz1f0oxtHiRzAKCPVmoUYDf+mvvm63ykCEw@mail.gmail.com>
- In-Reply-To
- <xmqq7dpr4qa0.fsf@gitster.c.googlers.com>
On Tue, Dec 8, 2020 at 7:22 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> > Elijah Newren <newren@gmail.com> writes: > > > ... As I said, I'm not sure why > > anyone would ever want to see diffs for merges and not for normal > > commits, the closest useful thing I can imagine is commit messages + > > diffs for just merges, stripping the normal commits. > > If I can run "git log --some-options master..next" (or more > realistically, over the range ko/next..next) to get individual > commits (without patch) and merges (only when --cc gives some > interesting nearby-changes), I would be very happy. But is there a > set of options that lets me do so?
So, you're saying you changed your mind since five years ago?[1] Or that what you said five years ago is still valid, but you'd appreciate more/different options that allow this new thing?
[1] https://lore.kernel.org/git/1440110591-12941-1-git-send-email-gitster@pobox.com/
We got to this point in this thread because Sergey suggested reverting the above change (as one option) in order to bring more consistency between -m and -c/--cc.