public inbox for
 help / color / mirror / Atom feed
From: Adam Dinwoodie <>
Subject: Updated: Git v2.38.0
Date: Tue, 4 Oct 2022 09:08:21 +0100	[thread overview]
Message-ID: <> (raw)

Version 2.38.0-1 of Git has been uploaded to the Cygwin distribution
servers, and should be coming soon to a mirror near you.

Git is a free and open source distributed version control system
designed to handle everything from small to very large projects with
speed and efficiency.

This is an update to the latest upstream release, and includes the
following packages:

- git
- git-cvs
- git-debuginfo
- git-email
- git-gui
- gitk
- git-p4
- git-svn

Selected extracts from the changelog:

> UI, Workflows & Features
>  * "git push" sometimes performs poorly when reachability bitmaps are
>    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 grep -m<max-hits>" is a way to limit the hits shown per file.
>  * "git mv A B" in a sparsely populated working tree can be asked to
>    move a path between directories that are "in cone" (i.e. expected
>    to be materialized in the working tree) and "out of cone"
>    (i.e. expected to be hidden).  The handling of such cases has been
>    improved.
>  * Introduce a safe.barerepository configuration variable that
>    allows users to forbid discovery of bare repositories.
>  * "git rebase -i" learns to update branches whose tip appear in the
>    rebased range with "--update-refs" option.
>  * "git rm" has become more aware of the sparse-index feature.
>  * "git rev-list --disk-usage" learned to take an optional value
>    "human" to show the reported value in human-readable format, like
>    "3.40MiB".
> Fixes since v2.37
> -----------------
>  * Rewrite of "git add -i" in C that appeared in Git 2.25 didn't
>    correctly record a removed file to the index, which was fixed.
>  * Fixes for tests when the source directory has unusual characters in
>    its path, e.g. whitespaces, double-quotes, etc.
>  * Platform-specific code that determines if a directory is OK to use
>    as a repository has been taught to report more details, especially
>    on Windows.

For a full list of the upstream changes in this release, please refer to
the upstream changelogs:



                 reply	other threads:[~2022-10-04  8:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).