| | 2 | {{{ |
| | 3 | Git v2.10.2 Release Notes |
| | 4 | ========================= |
| | 5 | |
| | 6 | Fixes since v2.10.1 |
| | 7 | ------------------- |
| | 8 | |
| | 9 | * The code that parses the format parameter of for-each-ref command |
| | 10 | has seen a micro-optimization. |
| | 11 | |
| | 12 | * The "graph" API used in "git log --graph" miscounted the number of |
| | 13 | output columns consumed so far when drawing a padding line, which |
| | 14 | has been fixed; this did not affect any existing code as nobody |
| | 15 | tried to write anything after the padding on such a line, though. |
| | 16 | |
| | 17 | * Almost everybody uses DEFAULT_ABBREV to refer to the default |
| | 18 | setting for the abbreviation, but "git blame" peeked into |
| | 19 | underlying variable bypassing the macro for no good reason. |
| | 20 | |
| | 21 | * Doc update to clarify what "log -3 --reverse" does. |
| | 22 | |
| | 23 | * An author name, that spelled a backslash-quoted double quote in the |
| | 24 | human readable part "My \"double quoted\" name", was not unquoted |
| | 25 | correctly while applying a patch from a piece of e-mail. |
| | 26 | |
| | 27 | * The original command line syntax for "git merge", which was "git |
| | 28 | merge <msg> HEAD <parent>...", has been deprecated for quite some |
| | 29 | time, and "git gui" was the last in-tree user of the syntax. This |
| | 30 | is finally fixed, so that we can move forward with the deprecation. |
| | 31 | |
| | 32 | * Codepaths that read from an on-disk loose object were too loose in |
| | 33 | validating what they are reading is a proper object file and |
| | 34 | sometimes read past the data they read from the disk, which has |
| | 35 | been corrected. H/t to Gustavo Grieco for reporting. |
| | 36 | |
| | 37 | * "git worktree", even though it used the default_abbrev setting that |
| | 38 | ought to be affected by core.abbrev configuration variable, ignored |
| | 39 | the variable setting. The command has been taught to read the |
| | 40 | default set of configuration variables to correct this. |
| | 41 | |
| | 42 | * A low-level function verify_packfile() was meant to show errors |
| | 43 | that were detected without dying itself, but under some conditions |
| | 44 | it didn't and died instead, which has been fixed. |
| | 45 | |
| | 46 | * When "git fetch" tries to find where the history of the repository |
| | 47 | it runs in has diverged from what the other side has, it has a |
| | 48 | mechanism to avoid digging too deep into irrelevant side branches. |
| | 49 | This however did not work well over the "smart-http" transport due |
| | 50 | to a design bug, which has been fixed. |
| | 51 | |
| | 52 | * When we started cURL to talk to imap server when a new enough |
| | 53 | version of cURL library is available, we forgot to explicitly add |
| | 54 | imap(s):// before the destination. To some folks, that didn't work |
| | 55 | and the library tried to make HTTP(s) requests instead. |
| | 56 | |
| | 57 | * The ./configure script generated from configure.ac was taught how |
| | 58 | to detect support of SSL by libcurl better. |
| | 59 | |
| | 60 | * http.emptyauth configuration is a way to allow an empty username to |
| | 61 | pass when attempting to authenticate using mechanisms like |
| | 62 | Kerberos. We took an unspecified (NULL) username and sent ":" |
| | 63 | (i.e. no username, no password) to CURLOPT_USERPWD, but did not do |
| | 64 | the same when the username is explicitly set to an empty string. |
| | 65 | |
| | 66 | * "git clone" of a local repository can be done at the filesystem |
| | 67 | level, but the codepath did not check errors while copying and |
| | 68 | adjusting the file that lists alternate object stores. |
| | 69 | |
| | 70 | * Documentation for "git commit" was updated to clarify that "commit |
| | 71 | -p <paths>" adds to the current contents of the index to come up |
| | 72 | with what to commit. |
| | 73 | |
| | 74 | * A stray symbolic link in $GIT_DIR/refs/ directory could make name |
| | 75 | resolution loop forever, which has been corrected. |
| | 76 | |
| | 77 | * The "submodule.<name>.path" stored in .gitmodules is never copied |
| | 78 | to .git/config and such a key in .git/config has no meaning, but |
| | 79 | the documentation described it and submodule.<name>.url next to |
| | 80 | each other as if both belong to .git/config. This has been fixed. |
| | 81 | |
| | 82 | * Recent git allows submodule.<name>.branch to use a special token |
| | 83 | "." instead of the branch name; the documentation has been updated |
| | 84 | to describe it. |
| | 85 | |
| | 86 | * In a worktree connected to a repository elsewhere, created via "git |
| | 87 | worktree", "git checkout" attempts to protect users from confusion |
| | 88 | by refusing to check out a branch that is already checked out in |
| | 89 | another worktree. However, this also prevented checking out a |
| | 90 | branch, which is designated as the primary branch of a bare |
| | 91 | reopsitory, in a worktree that is connected to the bare |
| | 92 | repository. The check has been corrected to allow it. |
| | 93 | |
| | 94 | * "git rebase" immediately after "git clone" failed to find the fork |
| | 95 | point from the upstream. |
| | 96 | |
| | 97 | * When fetching from a remote that has many tags that are irrelevant |
| | 98 | to branches we are following, we used to waste way too many cycles |
| | 99 | when checking if the object pointed at by a tag (that we are not |
| | 100 | going to fetch!) exists in our repository too carefully. |
| | 101 | |
| | 102 | * The Travis CI configuration we ship ran the tests with --verbose |
| | 103 | option but this risks non-TAP output that happens to be "ok" to be |
| | 104 | misinterpreted as TAP signalling a test that passed. This resulted |
| | 105 | in unnecessary failure. This has been corrected by introducing a |
| | 106 | new mode to run our tests in the test harness to send the verbose |
| | 107 | output separately to the log file. |
| | 108 | |
| | 109 | * Some AsciiDoc formatter mishandles a displayed illustration with |
| | 110 | tabs in it. Adjust a few of them in merge-base documentation to |
| | 111 | work around them. |
| | 112 | |
| | 113 | Also contains minor documentation updates and code clean-ups. |
| | 114 | }}} |
