From: Derrick Stolee <derrickstolee@github.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Jeff Hostetler <git@jeffhostetler.com>
Subject: Re: [ANNOUNCE] Git v2.37.0-rc0
Date: Tue, 14 Jun 2022 11:00:31 -0400 [thread overview]
Message-ID: <20999998-e369-8623-579c-a71527f9184e@github.com> (raw)
In-Reply-To: <xmqqwndk10gg.fsf@gitster.g>
On 6/13/2022 9:46 PM, Junio C Hamano wrote:
> * A workflow change for translators are being proposed. git.pot is
> no longer version controlled and it is local responsibility of
> translaters to generate it.
s/translaters/translators/
> * More fsmonitor--daemon.
Would you like to expand more here? Perhaps...
* The fsmonitor--daemon handles even more corner cases when
watching filesystem events.
CC'ing Jeff to see if he has thoughts.
> * The path taken by "git multi-pack-index" command from the end user
> was compared with path internally prepared by the tool withut first
> normalizing, which lead to duplicated paths not being noticed,
> which has been corrected.
s/withut/without/
> * Update a few end-user facing messages around eol conversion.
> (merge c970d30c2c ah/convert-warning-message later to maint).
optional: s/eol/EOL/
> * With a more targetted workaround in http.c in another topic, we may
> be able to lift this blanket "GCC12 dangling-pointer warning is
> broken and unsalvageable" workaround.
s/targetted/targeted/
Thanks for all your work to create this release!
-Stolee
next prev parent reply other threads:[~2022-06-14 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 1:46 [ANNOUNCE] Git v2.37.0-rc0 Junio C Hamano
2022-06-14 15:00 ` Derrick Stolee [this message]
2022-06-14 18:52 ` [PATCH] t3701: update tests fixed with builtin add -p Todd Zullinger
[not found] ` <0aff4d49e5934d11870a3c6bfecf1af0@SAMBXP02.univ-lyon1.fr>
2022-06-14 21:34 ` Matthieu Moy
2022-06-16 14:05 ` [ANNOUNCE] Git v2.37.0-rc0 Matthew John Cheetham
2022-06-16 18:13 ` 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
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=20999998-e369-8623-579c-a71527f9184e@github.com \
--to=derrickstolee@github.com \
--cc=git@jeffhostetler.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.
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).