From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Adam Dinwoodie" <adam@dinwoodie.org>,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
"Fangyi Zhou" <me@fangyi.io>,
"Josh Steadmon" <steadmon@google.com>,
"Martin Ågren" <martin.agren@gmail.com>,
"Todd Zullinger" <tmz@pobox.com>,
"Victoria Dye" <vdye@github.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.36.0-rc0
Date: Thu, 07 Apr 2022 18:20:33 -0700 [thread overview]
Message-ID: <xmqq1qy8qske.fsf@gitster.g> (raw)
In-Reply-To: xmqqo81gpokn.fsf@gitster.g
Junio C Hamano <gitster@pobox.com> writes:
> An early preview release Git v2.36.0-rc0 is now available for
> testing at the usual places. It is comprised of 661 non-merge
> commits since v2.35.0, contributed by 80 people, 25 of which are
> new faces [*].
Thanks for finding and fixing many oops glitches in this preview so
quickly. Hopefully with the tip of 'master/main' today, we can tag
a bug-free -rc1 tomorrow ;-)
$ git shortlog --no-merges v2.36.0-rc0..master
Adam Dinwoodie (1):
configure.ac: fix HAVE_SYNC_FILE_RANGE definition
Carlo Marcelo Arenas Belón (1):
git-compat-util: really support openssl as a source of entropy
Fangyi Zhou (1):
submodule-helper: fix usage string
Josh Steadmon (1):
ls-tree: `-l` should not imply recursive listing
Martin Ågren (1):
git-ls-tree.txt: fix the name of "%(objectsize:padded)"
Todd Zullinger (1):
doc: replace "--" with {litdd} in credential-cache/fsmonitor
Victoria Dye (1):
contrib/scalar: fix 'all' target in Makefile
Ævar Arnfjörð Bjarmason (2):
Documentation/Makefile: fix "make info" regression in dad9cd7d518
Documentation: add --batch-command to cat-file synopsis
next prev parent reply other threads:[~2022-04-08 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 20:43 [ANNOUNCE] Git v2.36.0-rc0 Junio C Hamano
2022-04-08 1:20 ` Junio C Hamano [this message]
2022-04-08 2:13 ` rsbecker
2022-04-08 8:29 ` Adam Dinwoodie
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=xmqq1qy8qske.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adam@dinwoodie.org \
--cc=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
--cc=me@fangyi.io \
--cc=steadmon@google.com \
--cc=tmz@pobox.com \
--cc=vdye@github.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).