4 Backward compatibility note
5 ---------------------------
7 The end-user facing Porcelain level commands in the "git diff" and
8 "git log" by default enables the rename detection; you can still use
9 "diff.renames" configuration variable to disable this.
11 Merging two branches that have no common ancestor with "git merge" is
12 by default forbidden now to prevent creating such an unusual merge by
15 The output formats of "git log" that indents the commit log message by
16 4 spaces now expands HT in the log message by default. You can use
17 the "--no-expand-tabs" option to disable this.
19 "git commit-tree" plumbing command required the user to always sign
20 its result when the user sets the commit.gpgsign configuration
21 variable, which was an ancient mistake, which this release corrects.
22 A script that drives commit-tree, if it relies on this mistake, now
23 needs to read commit.gpgsign and pass the -S option as necessary.
29 UI, Workflows & Features
31 * Comes with git-multimail 1.3.1 (in contrib/).
33 * The end-user facing Porcelain level commands like "diff" and "log"
34 now enables the rename detection by default.
36 * The credential.helper configuration variable is cumulative and
37 there is no good way to override it from the command line. As
38 a special case, giving an empty string as its value now serves
39 as the signal to clear the values specified in various files.
41 * A new "interactive.diffFilter" configuration can be used to
42 customize the diff shown in "git add -i" session.
44 * "git p4" now allows P4 author names to be mapped to Git author
47 * "git rebase -x" can be used without passing "-i" option.
49 * "git -c credential.<var>=<value> submodule" can now be used to
50 propagate configuration variables related to credential helper
51 down to the submodules.
53 * "git tag" can create an annotated tag without explicitly given an
54 "-a" (or "-s") option (i.e. when a tag message is given). A new
55 configuration variable, tag.forceSignAnnotated, can be used to tell
56 the command to create signed tag in such a situation.
58 * "git merge" used to allow merging two branches that have no common
59 base by default, which led to a brand new history of an existing
60 project created and then get pulled by an unsuspecting maintainer,
61 which allowed an unnecessary parallel history merged into the
62 existing project. The command has been taught not to allow this by
63 default, with an escape hatch "--allow-unrelated-histories" option
64 to be used in a rare event that merges histories of two projects
65 that started their lives independently.
67 * "git pull" has been taught to pass --allow-unrelated-histories
68 option to underlying "git merge".
70 * "git apply -v" learned to report paths in the patch that were
71 skipped via --include/--exclude mechanism or being outside the
72 current working directory.
74 * Shell completion (in contrib/) updates.
76 * The commit object name reported when "rebase -i" stops has been
79 * "git worktree add" can be given "--no-checkout" option to only
80 create an empty worktree without checking out the files.
82 * "git mergetools" learned to drive ExamDiff.
84 * "git pull --rebase" learned "--[no-]autostash" option, so that
85 the rebase.autostash configuration variable set to true can be
86 overridden from the command line.
88 * When "git log" shows the log message indented by 4-spaces, the
89 remainder of a line after a HT does not align in the way the author
90 originally intended. The command now expands tabs by default in
91 such a case, and allows the users to override it with a new option,
94 * "git send-email" now uses a more readable timestamps when
95 formulating a message ID.
97 * "git rerere" can encounter two or more files with the same conflict
98 signature that have to be resolved in different ways, but there was
99 no way to record these separate resolutions.
100 (merge 890fca8 jc/rerere-multi later to maint).
102 * "git p4" learned to record P4 jobs in Git commit that imports from
103 the history in Perforce.
105 * "git describe --contains" often made a hard-to-justify choice of
106 tag to give name to a given commit, because it tried to come up
107 with a name with smallest number of hops from a tag, causing an old
108 commit whose close descendant that is recently tagged were not
109 described with respect to an old tag but with a newer tag. It did
110 not help that its computation of "hop" count was further tweaked to
111 penalize being on a side branch of a merge. The logic has been
112 updated to favor using the tag with the oldest tagger date, which
113 is a lot easier to explain to the end users: "We describe a commit
114 in terms of the (chronologically) oldest tag that contains the
116 (merge 7550424 js/name-rev-use-oldest-ref later to maint).
118 * "git clone" learned "--shallow-submodules" option.
120 * HTTP transport clients learned to throw extra HTTP headers at the
121 server, specified via http.extraHeader configuration variable.
123 * Patch output from "git diff" and friends has been tweaked to be
124 more readable by using a blank line as a strong hint that the
125 contents before and after it belong to a logically separate unit.
127 * A new configuration variable core.hooksPath allows customizing
128 where the hook directory is.
130 * An earlier addition of "sanitize_submodule_env" with 14111fc4 (git:
131 submodule honor -c credential.* from command line, 2016-02-29)
132 turned out to be a convoluted no-op; implement what it wanted to do
133 correctly, and stop filtering settings given via "git -c var=val".
136 Performance, Internal Implementation, Development Support etc.
138 * The embedded args argv-array in the child process is used to build
139 the command line to run pack-objects instead of using a separate
142 * A test for tags has been restructured so that more parts of it can
143 easily be run on a platform without a working GnuPG.
145 * The startup_info data, which records if we are working inside a
146 repository (among other things), are now uniformly available to Git
147 subcommand implementations, and Git avoids attempting to touch
148 references when we are not in a repository.
150 * The command line argument parser for "receive-pack" has been
151 rewritten to use parse-options.
153 * A major part of "git submodule update" has been ported to C to take
154 advantage of the recently added framework to run download tasks in
157 * Rename bunch of tests on "git clone" for better organization.
159 * The tests that involve running httpd leaked the system-wide
160 configuration in /etc/gitconfig to the tested environment.
162 * Build updates for MSVC.
164 * The repository set-up sequence has been streamlined (the biggest
165 change is that there is no longer git_config_early()), so that we
166 do not attempt to look into refs/* when we know we do not have a
169 * Code restructuring around the "refs" area to prepare for pluggable
172 * Sources to many test helper binaries (and the generated helpers)
173 have been moved to t/helper/ subdirectory to reduce clutter at the
174 top level of the tree.
176 * Unify internal logic between "git tag -v" and "git verify-tag"
177 commands by making one directly call into the other.
178 (merge bef234b st/verify-tag later to maint).
180 * "merge-recursive" strategy incorrectly checked if a path that is
181 involved in its internal merge exists in the working tree.
183 * The test scripts for "git p4" (but not "git p4" implementation
184 itself) has been updated so that they would work even on a system
185 where the installed version of Python is python 3.
186 (merge 1fb3fb4 ld/p4-test-py3 later to maint).
188 * As nobody maintains our in-tree git.spec.in and distros use their
189 own spec file, we stopped pretending that we support "make rpm".
191 * Move from unsigned char[20] to struct object_id continues.
193 * Update of "git submodule" to move pieces of logic to C continues.
195 * The code for warning_errno/die_errno has been refactored and a new
196 error_errno() reporting helper is introduced.
197 (merge 1da045f nd/error-errno later to maint).
199 * Running tests with '-x' option to trace the individual command
200 executions is a useful way to debug test scripts, but some tests
201 that capture the standard error stream and check what the command
202 said can be broken with the trace output mixed in. When running
203 our tests under "bash", however, we can redirect the trace output
204 to another file descriptor to keep the standard error of programs
206 (merge d88785e jk/test-send-sh-x-trace-elsewhere later to maint).
209 Also contains various documentation updates and code clean-ups.
215 Unless otherwise noted, all the fixes since v2.8 in the maintenance
216 track are contained in this release (see the maintenance releases'
219 * "git config --get-urlmatch", unlike other variants of the "git
220 config --get" family, did not signal error with its exit status
221 when there was no matching configuration.
223 * The "--local-env-vars" and "--resolve-git-dir" options of "git
224 rev-parse" failed to work outside a repository when the command's
225 option parsing was rewritten in 1.8.5 era.
227 * "git index-pack --keep[=<msg>] pack-$name.pack" simply did not work.
229 * Fetching of history by naming a commit object name directly didn't
230 work across remote-curl transport.
232 * A small memory leak in an error codepath has been plugged in xdiff
235 * strbuf_getwholeline() did not NUL-terminate the buffer on certain
236 corner cases in its error codepath.
238 * "git mergetool" did not work well with conflicts that both sides
241 * "git send-email" had trouble parsing alias file in mailrc format
242 when lines in it had trailing whitespaces on them.
244 * When "git merge --squash" stopped due to conflict, the concluding
245 "git commit" failed to read in the SQUASH_MSG that shows the log
246 messages from all the squashed commits.
248 * "git merge FETCH_HEAD" dereferenced NULL pointer when merging
249 nothing into an unborn history (which is arguably unusual usage,
250 which perhaps was the reason why nobody noticed it).
252 * When "git worktree" feature is in use, "git branch -d" allowed
253 deletion of a branch that is checked out in another worktree,
256 * When "git worktree" feature is in use, "git branch -m" renamed a
257 branch that is checked out in another worktree without adjusting
258 the HEAD symbolic ref for the worktree.
260 * "git diff -M" used to work better when two originally identical
261 files A and B got renamed to X/A and X/B by pairing A to X/A and B
262 to X/B, but this was broken in the 2.0 timeframe.
264 * "git send-pack --all <there>" was broken when its command line
265 option parsing was written in the 2.6 timeframe.
267 * "git format-patch --help" showed `-s` and `--no-patch` as if these
268 are valid options to the command. We already hide `--patch` option
269 from the documentation, because format-patch is about showing the
270 diff, and the documentation now hides these options as well.
272 * When running "git blame $path" with unnormalized data in the index
273 for the path, the data in the working tree was blamed, even though
274 "git add" would not have changed what is already in the index, due
275 to "safe crlf" that disables the line-end conversion. It has been
278 * A change back in version 2.7 to "git branch" broke display of a
279 symbolic ref in a non-standard place in the refs/ hierarchy (we
280 expect symbolic refs to appear in refs/remotes/*/HEAD to point at
281 the primary branch the remote has, and as .git/HEAD to point at the
282 branch we locally checked out).
284 * A partial rewrite of "git submodule" in the 2.7 timeframe changed
285 the way the gitdir: pointer in the submodules point at the real
286 repository location to use absolute paths by accident. This has
289 * "git commit" misbehaved in a few minor ways when an empty message
290 is given via -m '', all of which has been corrected.
292 * Support for CRAM-MD5 authentication method in "git imap-send" did
295 * Upcoming OpenSSL 1.1.0 will break compilation b updating a few APIs
296 we use in imap-send, which has been adjusted for the change.
297 (merge 1245c74 ky/imap-send-openssl-1.1.0 later to maint).
299 * The socks5:// proxy support added back in 2.6.4 days was not aware
300 that socks5h:// proxies behave differently.
302 * "git config" had a codepath that tried to pass a NULL to
303 printf("%s"), which nobody seems to have noticed.
305 * On Cygwin, object creation uses the "create a temporary and then
306 rename it to the final name" pattern, not "create a temporary,
307 hardlink it to the final name and then unlink the temporary"
310 This is necessary to use Git on Windows shared directories, and is
311 already enabled for the MinGW and plain Windows builds. It also
312 has been used in Cygwin packaged versions of Git for quite a while.
313 See http://thread.gmane.org/gmane.comp.version-control.git/291853
315 * "merge-octopus" strategy did not ensure that the index is clean
318 * When "git merge" notices that the merge can be resolved purely at
319 the tree level (without having to merge blobs) and the resulting
320 tree happens to already exist in the object store, it forgot to
321 update the index, which lead to an inconsistent state for later
324 * "git submodule" reports the paths of submodules the command
325 recurses into, but this was incorrect when the command was not run
326 from the root level of the superproject.
327 (merge 2ab5660 sb/submodule-path-misc-bugs later to maint).
329 * The "user.useConfigOnly" configuration variable makes it an error
330 if users do not explicitly set user.name and user.email. However,
331 its check was not done early enough and allowed another error to
332 trigger, reporting that the default value we guessed from the
333 system setting was unusable. This was a suboptimal end-user
334 experience as we want the users to set user.name/user.email without
335 relying on the auto-detection at all.
336 (merge d3c06c1 da/user-useconfigonly later to maint).
338 * "git mv old new" did not adjust the path for a submodule that lives
339 as a subdirectory inside old/ directory correctly.
340 (merge a127331 sb/mv-submodule-fix later to maint).
342 * "git replace -e" did not honour "core.editor" configuration.
343 (merge 36b1437 js/replace-edit-use-editor-configuration later to maint).
345 * "git push" from a corrupt repository that attempts to push a large
346 number of refs deadlocked; the thread to relay rejection notices
347 for these ref updates blocked on writing them to the main thread,
348 after the main thread at the receiving end notices that the push
349 failed and decides not to read these notices and return a failure.
350 (merge f924b52a jk/push-client-deadlock-fix later to maint).
352 * mmap emulation on Windows has been optimized and work better without
353 consuming paging store when not needed.
354 (merge d5425d1 js/win32-mmap later to maint).
356 * A question by "git send-email" to ask the identity of the sender
358 (merge 0d6b21e jd/send-email-to-whom later to maint).
360 * UI consistency improvements for "git mergetool".
361 (merge cce076e nf/mergetool-prompt later to maint).
363 * "git rebase -m" could be asked to rebase an entire branch starting
364 from the root, but failed by assuming that there always is a parent
365 commit to the first commit on the branch.
366 (merge 79f4344 bw/rebase-merge-entire-branch later to maint).
368 * Fix a broken "p4 lfs" test.
369 (merge 9e220fe ls/p4-lfs-test-fix-2.7.0 later to maint).
371 * Recent update to Git LFS broke "git p4" by changing the output from
372 its "lfs pointer" subcommand.
373 (merge 82f2567 ls/p4-lfs later to maint).
375 * "git fetch" test t5510 was flaky while running a (forced) automagic
377 (merge bb05510 js/close-packs-before-gc later to maint).
379 * Documentation updates to help contributors setting up Travis CI
380 test for their patches.
381 (merge 0e5d028 ls/travis-submitting-patches later to maint).
383 * Some multi-byte encoding can have a backslash byte as a later part
384 of one letter, which would confuse "highlight" filter used in
386 (merge 029f372 sk/gitweb-highlight-encoding later to maint).
388 * "git commit-tree" plumbing command required the user to always sign
389 its result when the user sets the commit.gpgsign configuration
390 variable, which was an ancient mistake. Rework "git rebase" that
391 relied on this mistake so that it reads commit.gpgsign and pass (or
392 not pass) the -S option to "git commit-tree" to keep the end-user
393 expectation the same, while teaching "git commit-tree" to ignore
394 the configuration variable. This will stop requiring the users to
395 sign commit objects used internally as an implementation detail of
397 (merge 6694856 jc/commit-tree-ignore-commit-gpgsign later to maint).
399 * "http.cookieFile" configuration variable clearly wants a pathname,
400 but we forgot to treat it as such by e.g. applying tilde expansion.
401 (merge e5a39ad bn/http-cookiefile-config later to maint).
403 * Consolidate description of tilde-expansion that is done to
404 configuration variables that take pathname to a single place.
405 (merge dca83ab jc/config-pathname-type later to maint).
407 * Correct faulty recommendation to use "git submodule deinit ." when
408 de-initialising all submodules, which would result in a strange
409 error message in a pathological corner case.
410 (merge f6a5279 sb/submodule-deinit-all later to maint).
412 * Many 'linkgit:<git documentation page>' references were broken,
413 which are all fixed with this.
414 (merge 1cca17d jc/linkgit-fix later to maint).
416 * "git rerere" can get confused by conflict markers deliberately left
417 by the inner merge step, because they are indistinguishable from
418 the real conflict markers left by the outermost merge which are
419 what the end user and "rerere" need to look at. This was fixed by
420 making the conflict markers left by the inner merges a bit longer.
421 (merge 0f9fd5c jc/ll-merge-internal later to maint).
423 * CI test was taught to build documentation pages.
424 (merge b98712b ls/travis-build-doc later to maint).
426 * "git fsck" learned to catch NUL byte in a commit object as
427 potential error and warn.
428 (merge 6d2d780 jc/fsck-nul-in-commit later to maint).
430 * Portability enhancement for "rebase -i" to help platforms whose
431 shell does not like "for i in <empty>" (which is not POSIX-kosher).
432 (merge 8e98b35 jk/rebase-interative-eval-fix later to maint).
434 * On Windows, .git and optionally any files whose name starts with a
435 dot are now marked as hidden, with a core.hideDotFiles knob to
436 customize this behaviour.
437 (merge ebf31e7 js/windows-dotgit later to maint).
439 * Documentation for "git merge --verify-signatures" has been updated
440 to clarify that the signature of only the commit at the tip is
441 verified. Also the phrasing used for signature and key validity is
442 adjusted to align with that used by OpenPGP.
443 (merge 05a5869 kf/gpg-sig-verification-doc later to maint).
445 * Other minor clean-ups and documentation updates
446 (merge 8b5a3e9 kn/for-each-tag-branch later to maint).
447 (merge 99dab16 sb/misc-cleanups later to maint).
448 (merge 7a6a44c cc/apply later to maint).
449 (merge 6594883 nd/remove-unused later to maint).
450 (merge 0ff7410 sg/test-lib-simplify-expr-away later to maint).
451 (merge 060e776 jk/fix-attribute-macro-in-2.5 later to maint).
452 (merge d16df0c rt/string-list-lookup-cleanup later to maint).
453 (merge 376eb60 sb/config-exit-status-list later to maint).
454 (merge 9cea46c ew/doc-split-pack-disables-bitmap later to maint).
455 (merge fa72245 ew/normal-to-e later to maint).
456 (merge 2e39a24 rn/glossary-typofix later to maint).
457 (merge cadfbef sb/clean-test-fix later to maint).
458 (merge 832c0e5 lp/typofixes later to maint).
459 (merge f5ee54a sb/z-is-gnutar-ism later to maint).
460 (merge 2e3926b va/i18n-misc-updates later to maint).
461 (merge f212dcc bn/config-doc-tt-varnames later to maint).
462 (merge f54bea4 nd/remote-plural-ours-plus-theirs later to maint).
463 (merge 2bb0518 ak/t4151-ls-files-could-be-empty later to maint).
464 (merge 4df4313 jc/test-seq later to maint).
465 (merge a75a308 tb/t5601-sed-fix later to maint).
466 (merge 6c1fbe1 va/i18n-remote-comment-to-align later to maint).
467 (merge dee2303 va/mailinfo-doc-typofix later to maint).