7 Backward incompatible and other important changes
9 * The "pack-redundant" command, which has been left stale with almost
10 unusable performance issues, now warns loudly when it gets used, as
11 we no longer want to recommend its use (instead just "repack -d"
14 * The development community has adopted Contributor Covenant v2.0 to
15 update from v1.4 that we have been using.
17 * The support for deprecated PCRE1 library has been dropped.
20 UI, Workflows & Features
22 * The "--format=%(trailers)" mechanism gets enhanced to make it
23 easier to design output for machine consumption.
25 * When a user does not tell "git pull" to use rebase or merge, the
26 command gives a loud message telling a user to choose between
27 rebase or merge but creates a merge anyway, forcing users who would
28 want to rebase to redo the operation. Fix an early part of this
29 problem by tightening the condition to give the message---there is
30 no reason to stop or force the user to choose between rebase or
31 merge if the history fast-forwards.
33 * The configuration variable 'core.abbrev' can be set to 'no' to
34 force no abbreviation regardless of the hash algorithm.
36 * "git rev-parse" can be explicitly told to give output as absolute
37 or relative path with the `--path-format=(absolute|relative)` option.
39 * Bash completion (in contrib/) update to make it easier for
40 end-users to add completion for their custom "git" subcommands.
42 * "git maintenance" learned to drive scheduled maintenance on
43 platforms whose native scheduling methods are not 'cron'.
45 * After expiring a reflog and making a single commit, the reflog for
46 the branch would record a single entry that knows both @{0} and
47 @{1}, but we failed to answer "what commit were we on?", i.e. @{1}
49 * "git bundle" learns "--stdin" option to read its refs from the
50 standard input. Also, it now does not lose refs whey they point
53 * "git log" learned a new "--diff-merges=<how>" option.
55 * "git ls-files" can and does show multiple entries when the index is
56 unmerged, which is a source for confusion unless -s/-u option is in
57 use. A new option --deduplicate has been introduced.
59 * `git worktree list` now annotates worktrees as prunable, shows
60 locked and prunable attributes in --porcelain mode, and gained
63 * "git clone" tries to locally check out the branch pointed at by
64 HEAD of the remote repository after it is done, but the protocol
65 did not convey the information necessary to do so when copying an
66 empty repository. The protocol v2 learned how to do so.
68 * There are other ways than ".." for a single token to denote a
69 "commit range", namely "<rev>^!" and "<rev>^-<n>", but "git
70 range-diff" did not understand them.
72 * The "git range-diff" command learned "--(left|right)-only" option
73 to show only one side of the compared range.
75 * "git mergetool" feeds three versions (base, local and remote) of
76 a conflicted path unmodified. The command learned to optionally
77 prepare these files with unconflicted parts already resolved.
79 * The .mailmap is documented to be read only from the root level of a
80 working tree, but a stray file in a bare repository also was read
81 by accident, which has been corrected.
83 * "git maintenance" tool learned a new "pack-refs" maintenance task.
85 * The error message given when a configuration variable that is
86 expected to have a boolean value has been improved.
88 * Signed commits and tags now allow verification of objects, whose
89 two object names (one in SHA-1, the other in SHA-256) are both
92 * "git rev-list" command learned "--disk-usage" option.
94 * "git {diff,log} --{skip,rotate}-to=<path>" allows the user to
95 discard diff output for early paths or move them to the end of the
98 * "git difftool" learned "--skip-to=<path>" option to restart an
99 interrupted session from an arbitrary path.
101 * "git grep" has been tweaked to be limited to the sparse checkout
104 * "git rebase --[no-]fork-point" gained a configuration variable
105 rebase.forkPoint so that users do not have to keep specifying a
109 Performance, Internal Implementation, Development Support etc.
111 * A 3-year old test that was not testing anything useful has been
114 * Retire more names with "sha1" in it.
116 * The topological walk codepath is covered by new trace2 stats.
118 * Update the Code-of-conduct to version 2.0 from the upstream (we've
119 been using version 1.4).
121 * "git mktag" validates its input using its own rules before writing
122 a tag object---it has been updated to share the logic with "git
125 * Two new ways to feed configuration variable-value pairs via
126 environment variables have been introduced, and the way
127 GIT_CONFIG_PARAMETERS encodes variable/value pairs has been tweaked
128 to make it more robust.
130 * Tests have been updated so that they do not to get affected by the
131 name of the default branch "git init" creates.
133 * "git fetch" learns to treat ref updates atomically in all-or-none
134 fashion, just like "git push" does, with the new "--atomic" option.
136 * The peel_ref() API has been replaced with peel_iterated_oid().
138 * The .use_shell flag in struct child_process that is passed to
139 run_command() API has been clarified with a bit more documentation.
141 * Document, clean-up and optimize the code around the cache-tree
142 extension in the index.
144 * The ls-refs protocol operation has been optimized to narrow the
145 sub-hierarchy of refs/ it walks to produce response.
147 * When removing many branches and tags, the code used to do so one
148 ref at a time. There is another API it can use to delete multiple
149 refs, and it makes quite a lot of performance difference when the
152 * The "pack-objects" command needs to iterate over all the tags when
153 automatic tag following is enabled, but it actually iterated over
154 all refs and then discarded everything outside "refs/tags/"
155 hierarchy, which was quite wasteful.
157 * A perf script was made more portable.
159 * Our setting of GitHub CI test jobs were a bit too eager to give up
160 once there is even one failure found. Tweak the knob to allow
161 other jobs keep running even when we see a failure, so that we can
162 find more failures in a single run.
164 * We've carried compatibility codepaths for compilers without
165 variadic macros for quite some time, but the world may be ready for
166 them to be removed. Force compilation failure on exotic platforms
167 where variadic macros are not available to find out who screams in
168 such a way that we can easily revert if it turns out that the world
171 * Code clean-up to ensure our use of hashtables using object names as
172 keys use the "struct object_id" objects, not the raw hash values.
174 * Lose the debugging aid that may have been useful in the past, but
175 no longer is, in the "grep" codepaths.
177 * Some pretty-format specifiers do not need the data in commit object
178 (e.g. "%H"), but we were over-eager to load and parse it, which has
179 been made even lazier.
181 * Get rid of "GETTEXT_POISON" support altogether, which may or may
182 not be controversial.
184 * Introduce an on-disk file to record revindex for packdata, which
185 traditionally was always created on the fly and only in-core.
187 * The commit-graph learned to use corrected commit dates instead of
188 the generation number to help topological revision traversal.
190 * Piecemeal of rewrite of "git bisect" in C continues.
192 * When a pager spawned by us exited, the trace log did not record its
193 exit status correctly, which has been corrected.
195 * Removal of GIT_TEST_GETTEXT_POISON continues.
197 * The code to implement "git merge-base --independent" was poorly
198 done and was kept from the very beginning of the feature.
204 * Diagnose command line error of "git rebase" early.
206 * Clean up option descriptions in "git cmd --help".
208 * "git stash" did not work well in a sparsely checked out working
211 * Some tests expect that "ls -l" output has either '-' or 'x' for
212 group executable bit, but setgid bit can be inherited from parent
213 directory and make these fields 'S' or 's' instead, causing test
216 * "git for-each-repo --config=<var> <cmd>" should not run <cmd> for
217 any repository when the configuration variable <var> is not defined
220 * Fix 2.29 regression where "git mergetool --tool-help" fails to list
221 all the available tools.
223 * Fix for procedure to building CI test environment for mac.
225 * The implementation of "git branch --sort" wrt the detached HEAD
226 display has always been hacky, which has been cleaned up.
228 * Newline characters in the host and path part of git:// URL are
231 * "git diff" showed a submodule working tree with untracked cruft as
232 "Submodule commit <objectname>-dirty", but a natural expectation is
233 that the "-dirty" indicator would align with "git describe --dirty",
234 which does not consider having untracked files in the working tree
235 as source of dirtiness. The inconsistency has been fixed.
237 * When more than one commit with the same patch ID appears on one
238 side, "git log --cherry-pick A...B" did not exclude them all when a
239 commit with the same patch ID appears on the other side. Now it
242 * Documentation for "git fsck" lost stale bits that has become
245 * Doc fix for packfile URI feature.
247 * When "git rebase -i" processes "fixup" insn, there is no reason to
248 clean up the commit log message, but we did the usual stripspace
249 processing. This has been corrected.
250 (merge f7d42ceec5 js/rebase-i-commit-cleanup-fix later to maint).
252 * Fix in passing custom args from "git clone" to "upload-pack" on the
254 (merge ad6b5fefbd jv/upload-pack-filter-spec-quotefix later to maint).
256 * The command line completion (in contrib/) completed "git branch -d"
257 with branch names, but "git branch -D" offered tagnames in addition,
258 which has been corrected. "git branch -M" had the same problem.
259 (merge 27dc071b9a jk/complete-branch-force-delete later to maint).
261 * When commands are started from a subdirectory, they may have to
262 compare the path to the subdirectory (called prefix and found out
263 from $(pwd)) with the tracked paths. On macOS, $(pwd) and
264 readdir() yield decomposed path, while the tracked paths are
265 usually normalized to the precomposed form, causing mismatch. This
266 has been fixed by taking the same approach used to normalize the
267 command line arguments.
268 (merge 5c327502db tb/precompose-prefix-too later to maint).
270 * Even though invocations of "die()" were logged to the trace2
271 system, "BUG()"s were not, which has been corrected.
272 (merge 0a9dde4a04 jt/trace2-BUG later to maint).
274 * "git grep --untracked" is meant to be "let's ALSO find in these
275 files on the filesystem" when looking for matches in the working
276 tree files, and does not make any sense if the primary search is
277 done against the index, or the tree objects. The "--cached" and
278 "--untracked" options have been marked as mutually incompatible.
279 (merge 0c5d83b248 mt/grep-cached-untracked later to maint).
281 * Fix "git fsck --name-objects" which apparently has not been used by
282 anybody who is motivated enough to report breakage.
283 (merge e89f89361c js/fsck-name-objects-fix later to maint).
285 * Avoid individual tests in t5411 from getting affected by each other
286 by forcing them to use separate output files during the test.
287 (merge 822ee894f6 jx/t5411-unique-filenames later to maint).
289 * Test to make sure "git rev-parse one-thing one-thing" gives
290 the same thing twice (when one-thing is --since=X).
291 (merge a5cdca4520 ew/rev-parse-since-test later to maint).
293 * When certain features (e.g. grafts) used in the repository are
294 incompatible with the use of the commit-graph, we used to silently
295 turned commit-graph off; we now tell the user what we are doing.
296 (merge c85eec7fc3 js/commit-graph-warning later to maint).
298 * Objects that lost references can be pruned away, even when they
299 have notes attached to it (and these notes will become dangling,
300 which in turn can be pruned with "git notes prune"). This has been
301 clarified in the documentation.
302 (merge fa9ab027ba mz/doc-notes-are-not-anchors later to maint).
304 * The error codepath around the "--temp/--prefix" feature of "git
305 checkout-index" has been improved.
306 (merge 3f7ba60350 mt/checkout-index-corner-cases later to maint).
308 * The "git maintenance register" command had trouble registering bare
309 repositories, which had been corrected.
311 * A handful of multi-word configuration variable names in
312 documentation that are spelled in all lowercase have been corrected
313 to use the more canonical camelCase.
314 (merge 7dd0eaa39c dl/doc-config-camelcase later to maint).
316 * "git push $there --delete ''" should have been diagnosed as an
317 error, but instead turned into a matching push, which has been
319 (merge 20e416409f jc/push-delete-nothing later to maint).
321 * Other code cleanup, docfix, build fix, etc.
322 (merge e3f5da7e60 sg/t7800-difftool-robustify later to maint).
323 (merge 9d336655ba js/doc-proto-v2-response-end later to maint).
324 (merge 1b5b8cf072 jc/maint-column-doc-typofix later to maint).
325 (merge 3a837b58e3 cw/pack-config-doc later to maint).
326 (merge 01168a9d89 ug/doc-commit-approxidate later to maint).
327 (merge b865734760 js/params-vs-args later to maint).
projects / git / blob