This update for git fixes the following issues:
Update from version 2.26.2 to version 2.31.1 (jsc#SLE-18152)
Security fixes:
Non security changes:
sysusers
file to create git-daemon
user.perl-base
and openssh-server
dependency on git-core
and provide a perl-Git
package. (jsc#SLE-17838)fsmonitor
bug fixesgit bisect
to take an annotated tag as a good/bad endpointgit mv
on case insensitive systemsopenssh-clients
where possible (like Tumbleweed or SUSE Linux Enterprise >= 15 SP3). (bsc#1183580)rsync
requirement, not necessary anymore.pack-redundant
command is discouraged and will trigger a warning. The replacement is repack -d
.--format=%(trailers)
mechanism gets enhanced to make it easier to design output for machine consumption.fast-forwards
.core.abbrev
can be set to no
to force no abbreviation regardless of the hash algorithmgit rev-parse
can be explicitly told to give output as absolute or relative path with the
--path-format=(absolute|relative)
option.git
subcommands.git maintenance
learned to drive scheduled maintenance on platforms whose native scheduling methods are not 'cron'.@{0}
and @{1}
, but we failed to answer 'what commit were we on?', i.e. @{1}
git bundle
learns --stdin
option to read its refs from the standard input.git log
learned a new --diff-merges=<how>
option.git ls-files
can and does show multiple entries when the index is unmerged, which is a source for confusion
unless -s/-u
option is in use. A new option --deduplicate
has been introduced.git worktree list
now annotates worktrees as prunable, shows locked and prunable attributes
in --porcelain mode
, and gained a --verbose
option.git clone
tries to locally check out the branch pointed at by HEAD of the remote repository after it
is done, but the protocol did not convey the information necessary to do so when copying an empty repository...
for a single token to denote a commit range', namely
<rev>^!
and
<rev>^-<n>, but
git range-diff` did not understand them.git range-diff
command learned --(left|right)-only
option to show only one side of the compared range.git mergetool
feeds three versions (base, local and remote) of a conflicted path unmodified.
The command learned to optionally prepare these files with unconflicted parts already resolved..mailmap
is documented to be read only from the root level of a working tree, but a stray file
in a bare repository also was read by accident, which has been corrected.git maintenance
tool learned a new pack-refs
maintenance task.git rev-list
command learned --disk-usage
option.git diff
, git log
--{skip,rotate}-to=<path>
allows the user to discard diff output for early
paths or move them to the end of the output.git difftool
learned --skip-to=<path>
option to restart an interrupted session from an arbitrary path.git grep
has been tweaked to be limited to the sparse checkout paths.git rebase --[no-]fork-point
gained a configuration variable rebase.forkPoint
so that users do not have
to keep specifying a non-default setting.git stash
did not work well in a sparsely checked out working tree.git://
URL are now forbidden.Userdiff
updates for PHP, Rust, CSSgit push --force-with-lease[=<ref>]
by
introducing --force-if-includes
asciidoctor
for the default ruby version--committer-date-is-author-date
option of rebase
and am
subcommands lost the e-mail address by
mistake in 2.29git worktree
gained a repair
subcommand, git init --separate-git-dir
no longer corrupts administrative data
related to linked worktreesgit maintenance
introduced for repository maintenance tasksfetch.writeCommitGraph
is deemed to be still a bit too risky and is no longer part of the
feature.experimental
set.diff
family honors the diff.relative
configuration variable.git diff-files
has been taught to say paths that are marked as intent-to-add
are new files,
not modified from an empty blob.git gui
now allows opening work trees from the start-up dialog.git bugreport
reports what shell is in use.git fast-import
has an option to pass
these timestamps intact to allow recreating existing repositories as-is.git describe
will always use the long
version when giving its output based misplaced tags git pull
issues a warning message until the pull.rebase
configuration variable is explicitly given{ "binaries": [ { "git-core": "2.31.1-10.3.1", "perl-Git": "2.31.1-10.3.1", "git-email": "2.31.1-10.3.1", "git": "2.31.1-10.3.1", "gitk": "2.31.1-10.3.1", "git-credential-gnome-keyring": "2.31.1-10.3.1", "git-daemon": "2.31.1-10.3.1", "git-doc": "2.31.1-10.3.1", "git-cvs": "2.31.1-10.3.1", "git-arch": "2.31.1-10.3.1", "git-web": "2.31.1-10.3.1", "git-p4": "2.31.1-10.3.1", "git-credential-libsecret": "2.31.1-10.3.1", "git-svn": "2.31.1-10.3.1", "git-gui": "2.31.1-10.3.1" } ] }