git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.33.0-rc2
Date: Sat, 14 Aug 2021 10:00:08 -0700	[thread overview]
Message-ID: <xmqq5yw8ufl3.fsf@gitster.g> (raw)
In-Reply-To: <CAN0heSrPXdpPXTpY3Cdn-HHcuzLvc--Y_L+SgK-QGt5yS8u54w@mail.gmail.com> ("Martin Ågren"'s message of "Sat, 14 Aug 2021 10:01:49 +0200")

Martin Ågren <martin.agren@gmail.com> writes:

> On Thu, 12 Aug 2021 at 01:23, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Git 2.33 Release Notes (draft)
>> ==============================
>
> rc1 had a section "Backward compatibility notes" where the recent work
> on "git log -m" was mentioned. That was then dropped because of
> 6a38e33331 ("Revert 'diff-merges: let "-m" imply "-p"'", 2021-08-05), so
> there are no backward compatibility notes in rc2.
>
>> Updates since Git 2.32
>> ----------------------
>>
>> UI, Workflows & Features
>
>>  * The "-m" option in "git log -m" that does not specify which format,
>>    if any, of diff is desired did not have any visible effect; it now
>>    implies some form of diff (by default "--patch") is produced.
>
> This is basically the same blurb. It was duplicated in rc1, and one of
> the copies remains in rc2. I believe it should be dropped.

It indeed is now stale and needs to be adjusted.

Thanks for your sharp eyes.


      reply	other threads:[~2021-08-14 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 23:22 [ANNOUNCE] Git v2.33.0-rc2 Junio C Hamano
2021-08-14  8:01 ` Martin Ågren
2021-08-14 17:00   ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5yw8ufl3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.agren@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).