From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.30.0-rc2
Date: Thu, 24 Dec 2020 07:13:57 +0100 [thread overview]
Message-ID: <CAP8UFD3aHEpHZWxzwz=RQr7DNAmJhLeoiOzubRqk1=7gRyG4_g@mail.gmail.com> (raw)
In-Reply-To: <xmqqtusc5djv.fsf@gitster.c.googlers.com>
Most of the suggestions below are found by GMail.
On Thu, Dec 24, 2020 at 12:08 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> A release candidate Git v2.30.0-rc2 is now available for testing
> at the usual places. It is comprised of 19 non-merge commits since
Maybe: s/is comprised of/comprises/
> v2.30.0-rc1, contributed by 5 people, none of which are new faces.
[..]
> * Various subcommands of "git config" that takes value_regex
s/takes/take/
> learn the "--literal-value" option to take the value_regex option
s/learn/learned/
> as a literal string.
[...]
> * More preliminary tests have been added to document desired outcome
s/outcome/outcomes/
> of various "directory rename" situations.
[...]
> * The code to see if "git stash drop" can safely remove refs/stash
> has been made more carerful.
s/carerful/careful/
> (merge 4f44c5659b rs/empty-reflog-check-fix later to maint).
[...]
> * Since jgit does not yet work with SHA-256 repositories, mark the
> tests that uses it not to run unless we are testing with ShA-1
s/uses/use/
> repositories.
> (merge ea699b4adc sg/t5310-jgit-wants-sha1 later to maint).
[...]
> * "git apply" adjusted the permission bits of working-tree files and
> directories according core.sharedRepository setting by mistake and
s/according/according to/
> for a long time, which has been corrected.
> (merge eb3c027e17 mt/do-not-use-scld-in-working-tree later to maint).
[...]
> * "git pack-redandant" when there is only one packfile used to crash,
s/pack-redandant/pack-redundant/
> which has been corrected.
> (merge 0696232390 jx/pack-redundant-on-single-pack later to maint).
next prev parent reply other threads:[~2020-12-24 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 23:05 [ANNOUNCE] Git v2.30.0-rc2 Junio C Hamano
2020-12-24 0:22 ` Todd Zullinger
2020-12-24 0:48 ` Junio C Hamano
2020-12-24 6:13 ` Christian Couder [this message]
2020-12-24 6:28 ` Junio C Hamano
2020-12-24 6:36 ` Junio C Hamano
2020-12-24 14:49 ` Randall S. Becker
2020-12-24 15:16 ` Felipe Contreras
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='CAP8UFD3aHEpHZWxzwz=RQr7DNAmJhLeoiOzubRqk1=7gRyG4_g@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/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).