summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/2.15.2.txt
blob: b480e56b684de64c68013025bdd0165e2ffbf1dc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Git v2.15.2 Release Notes
=========================

Fixes since v2.15.1
-------------------

 * Recent update to the refs infrastructure implementation started
   rewriting packed-refs file more often than before; this has been
   optimized again for most trivial cases.

 * The SubmittingPatches document has been converted to produce an
   HTML version via AsciiDoc/Asciidoctor.

 * Contrary to the documentation, "git pull -4/-6 other-args" did not
   ask the underlying "git fetch" to go over IPv4/IPv6, which has been
   corrected.

 * When "git rebase" prepared an mailbox of changes and fed it to "git
   am" to replay them, it was confused when a stray "From " happened
   to be in the log message of one of the replayed changes.  This has
   been corrected.

 * Command line completion (in contrib/) has been taught about the
   "--copy" option of "git branch".

 * "git apply --inaccurate-eof" when used with "--ignore-space-change"
   triggered an internal sanity check, which has been fixed.

 * The sequencer machinery (used by "git cherry-pick A..B", and "git
   rebase -i", among other things) would have lost a commit if stopped
   due to an unlockable index file, which has been fixed.

 * The three-way merge performed by "git cherry-pick" was confused
   when a new submodule was added in the meantime, which has been
   fixed (or "papered over").

 * "git notes" sent its error message to its standard output stream,
   which was corrected.

 * A few scripts (both in production and tests) incorrectly redirected
   their error output.  These have been corrected.

 * Clarify and enhance documentation for "merge-base --fork-point", as
   it was clear what it computed but not why/what for.

 * This release also contains the fixes made in the v2.13.7 version of
   Git.  See its release notes for details.


Also contains various documentation updates and code clean-ups.