Accepting request 1127934 from devel:tools:scm
- update to 2.43.0: * The "--rfc" option of "git format-patch" used to be a valid way to override an earlier "--subject-prefix=<something>" on the command line and replace it with "[RFC PATCH]", but from this release, it merely prefixes the string "RFC " in front of the given subject prefix. If you are negatively affected by this change, please use "--subject-prefix=PATCH --rfc" as a replacement. * In Git 2.42, "git rev-list --stdin" learned to take non-revisions (like "--not") from the standard input, but the way such a "--not" was handled was quite confusing, which has been rethought. The updated rule is that "--not" given from the command line only affects revs given from the command line that comes but not revs read from the standard input, and "--not" read from the standard input affects revs given from the standard input and not revs given from the command line. * A message written in olden time prevented a branch from getting checked out, saying it is already checked out elsewhere. But these days, we treat a branch that is being bisected or rebased just like a branch that is checked out and protect it from getting modified with the same codepath. The message has been rephrased to say that the branch is "in use" to avoid confusion. * Hourly and other schedules of "git maintenance" jobs are randomly distributed now. * "git cmd -h" learned to signal which options can be negated by listing such options like "--[no-]opt". * The way authentication related data other than passwords (e.g., oauth token and password expiration data) are stored in libsecret keyrings has been rethought. * Update the libsecret and wincred credential helpers to correctly match which credential to erase; they erased the wrong entry in OBS-URL: https://build.opensuse.org/request/show/1127934 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/git?expand=0&rev=304
This commit is contained in:
commit
25f2472069
Binary file not shown.
BIN
git-2.42.1.tar.xz
(Stored with Git LFS)
BIN
git-2.42.1.tar.xz
(Stored with Git LFS)
Binary file not shown.
BIN
git-2.43.0.tar.sign
Normal file
BIN
git-2.43.0.tar.sign
Normal file
Binary file not shown.
3
git-2.43.0.tar.xz
Normal file
3
git-2.43.0.tar.xz
Normal file
@ -0,0 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5446603e73d911781d259e565750dcd277a42836c8e392cac91cf137aa9b76ec
|
||||
size 7382996
|
86
git.changes
86
git.changes
@ -1,7 +1,91 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Nov 21 14:52:03 UTC 2023 - Dirk Müller <dmueller@suse.com>
|
||||
|
||||
- update to 2.43.0:
|
||||
* The "--rfc" option of "git format-patch" used to be a valid way to
|
||||
override an earlier "--subject-prefix=<something>" on the command
|
||||
line and replace it with "[RFC PATCH]", but from this release, it
|
||||
merely prefixes the string "RFC " in front of the given subject
|
||||
prefix. If you are negatively affected by this change, please use
|
||||
"--subject-prefix=PATCH --rfc" as a replacement.
|
||||
* In Git 2.42, "git rev-list --stdin" learned to take non-revisions
|
||||
(like "--not") from the standard input, but the way such a "--not" was
|
||||
handled was quite confusing, which has been rethought. The updated
|
||||
rule is that "--not" given from the command line only affects revs
|
||||
given from the command line that comes but not revs read from the
|
||||
standard input, and "--not" read from the standard input affects
|
||||
revs given from the standard input and not revs given from the
|
||||
command line.
|
||||
* A message written in olden time prevented a branch from getting
|
||||
checked out, saying it is already checked out elsewhere. But these
|
||||
days, we treat a branch that is being bisected or rebased just like
|
||||
a branch that is checked out and protect it from getting modified
|
||||
with the same codepath. The message has been rephrased to say that
|
||||
the branch is "in use" to avoid confusion.
|
||||
* Hourly and other schedules of "git maintenance" jobs are randomly
|
||||
distributed now.
|
||||
* "git cmd -h" learned to signal which options can be negated by
|
||||
listing such options like "--[no-]opt".
|
||||
* The way authentication related data other than passwords (e.g.,
|
||||
oauth token and password expiration data) are stored in libsecret
|
||||
keyrings has been rethought.
|
||||
* Update the libsecret and wincred credential helpers to correctly
|
||||
match which credential to erase; they erased the wrong entry in
|
||||
some cases.
|
||||
* Git GUI updates.
|
||||
* "git format-patch" learned a new "--description-file" option that
|
||||
lets cover letter description to be fed; this can be used on
|
||||
detached HEAD where there is no branch description available, and
|
||||
also can override the branch description if there is one.
|
||||
* Use of the "--max-pack-size" option to allow multiple packfiles to
|
||||
be created is now supported even when we are sending unreachable
|
||||
objects to cruft packs.
|
||||
* "git format-patch --rfc --subject-prefix=<foo>" used to ignore the
|
||||
"--subject-prefix" option and used "[RFC PATCH]"; now we will add
|
||||
"RFC" prefix to whatever subject prefix is specified.
|
||||
* "git log --format" has been taught the %(decorate) placeholder for
|
||||
further customization over what the "--decorate" option offers.
|
||||
* The default log message created by "git revert", when reverting a
|
||||
commit that records a revert, has been tweaked, to encourage people
|
||||
to describe complex "revert of revert of revert" situations better in
|
||||
their own words.
|
||||
* The command-line completion support (in contrib/) learned to
|
||||
complete "git commit --trailer=" for possible trailer keys.
|
||||
* "git update-index" learned the "--show-index-version" option to
|
||||
inspect the index format version used by the on-disk index file.
|
||||
* "git diff" learned the "diff.statNameWidth" configuration variable,
|
||||
to give the default width for the name part in the "--stat" output.
|
||||
* "git range-diff --notes=foo" compared "log --notes=foo --notes" of
|
||||
the two ranges, instead of using just the specified notes tree,
|
||||
which has been corrected to use only the specified notes tree.
|
||||
* The command line completion script (in contrib/) can be told to
|
||||
complete aliases by including ": git <cmd> ;" in the alias to tell
|
||||
it that the alias should be completed in a similar way to how "git
|
||||
<cmd>" is completed. The parsing code for the alias has been
|
||||
loosened to allow ';' without an extra space before it.
|
||||
* "git for-each-ref" and friends learned to apply mailmap to
|
||||
authorname and other fields in a more flexible way than using
|
||||
separate placeholder letters like %a[eElL] every time we want to
|
||||
come up with small variants.
|
||||
* "git repack" machinery learned to pay attention to the "--filter="
|
||||
option.
|
||||
* "git repack" learned the "--max-cruft-size" option to prevent cruft
|
||||
packs from growing without bounds.
|
||||
* "git merge-tree" learned to take strategy backend specific options
|
||||
via the "-X" option, like "git merge" does.
|
||||
* "git log" and friends learned the "--dd" option that is a
|
||||
short-hand for "--diff-merges=first-parent -p".
|
||||
* The attribute subsystem learned to honor the "attr.tree"
|
||||
configuration variable that specifies which tree to read the
|
||||
.gitattributes files from.
|
||||
* "git merge-file" learns a mode to read three variants of the
|
||||
contents to be merged from blob objects.
|
||||
* see https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.43.0.txt
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Sat Nov 4 12:15:19 UTC 2023 - Andreas Stieger <andreas.stieger@gmx.de>
|
||||
|
||||
- git 2.24.1:
|
||||
- git 2.42.1:
|
||||
* The usual number of bug fixes, including
|
||||
* Fix "git diff" exit code handling
|
||||
* Various fixes to the behavior of "rebase -i" when the command
|
||||
|
Loading…
Reference in New Issue
Block a user