From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.38.0-rc0
Date: Mon, 19 Sep 2022 23:24:02 +0700 [thread overview]
Message-ID: <YyiXojfvwfvmW4Dd@danh.dev> (raw)
In-Reply-To: <xmqqczbwkpt8.fsf@gitster.g>
On 2022-09-15 19:37:07-0700, Junio C Hamano <gitster@pobox.com> wrote:
> UI, Workflows & Features
>
> * "git remote show [-n] frotz" now pays attention to negative
> pathspec.
>
> * "git push" sometimes perform poorly when reachability bitmaps are
I see that most reference to command use third singular form.
Maybe s/perform/&s/
> used, even in a repository where other operations are helped by
> bitmaps. The push.useBitmaps configuration variable is introduced
> to allow disabling use of reachability bitmaps only for "git push".
[...]
> * "git format-patch --from=<ident>" can be told to add an in-body
> "From:" line even for commits that are authored by the given
> <ident> with "--force-in-body-from"option.
Maybe a space between last double-quote '"' and 'option'
[...]
> Performance, Internal Implementation, Development Support etc.
>
> * Apply Coccinelle rule to turn raw memmove() into MOVE_ARRAY() cpp
> macro, which would improve maintainability and readability.
[...]
> * A coccinelle rule (in contrib/) to encourage use of COPY_ARRAY
> macro has been improved.
Maybe title-case 'coccinelle' for consistency.
> Fixes since v2.37
> -----------------
[...]
> * "git fsck" reads mode from tree objects but canonicalizes the mode
> before passing it to the logic to check object sanity, which has
> hid broken tree objects from the checking logic. This has been
> corrected, but to help exiting projects with broken tree objects
s/exiting/existing/ perhap?
> that they cannot fix retroactively, the severity of anomalies this
> code detects has been demoted to "info" for now.
--
Danh
next prev parent reply other threads:[~2022-09-19 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 2:37 [ANNOUNCE] Git v2.38.0-rc0 Junio C Hamano
2022-09-16 6:38 ` Todd Zullinger
2022-09-16 15:47 ` Junio C Hamano
2022-09-19 16:24 ` Đoàn Trần Công Danh [this message]
2022-09-19 18:04 ` 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=YyiXojfvwfvmW4Dd@danh.dev \
--to=congdanhqx@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).