Most of the suggestions below are found by GMail. On Thu, Dec 24, 2020 at 12:08 AM Junio C Hamano <gitster@xxxxxxxxx> 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).
