9 * Building on older MacOS X systems automatically sets
10 the necessary NO_APPLE_COMMON_CRYPTO build-time option.
13 UI, Workflows & Features
15 * "git config --edit --global" starts from a skeletal per-user
16 configuration file contents, instead of a total blank, when the
17 user does not already have any. This immediately reduces the
18 need for a later "Have you forgotten setting core.user?" and we
19 can add more to the template as we gain more experience.
21 * "git stash list -p" used to be almost always a no-op because each
22 stash entry is represented as a merge commit. It learned to show
23 the difference between the base commit version and the working tree
24 version, which is in line with what "git show" gives.
26 Performance, Internal Implementation, etc.
28 * In tests, we have been using NOT_{MINGW,CYGWIN} test prerequisites
29 long before negated prerequisites e.g. !MINGW were invented.
30 The former has been converted to the latter to avoid confusion.
32 * Looking up remotes configuration in a repository with very many
33 remotes defined has been optimized.
35 * There are cases where you lock and open to write a file, close it
36 to show the updated contents to external processes, and then have
37 to update the file again while still holding the lock, but the
38 lockfile API lacked support for such an access pattern.
40 * An in-core caching layer to let us avoid reading the same
41 configuration files number of times has been added.
43 * Various code paths have been cleaned up and simplified by using
44 "strbuf", "starts_with()", and "skip_prefix()" APIs more.
47 Also contains various documentation updates and code clean-ups.
53 Unless otherwise noted, all the fixes since v2.1 in the maintenance
54 track are contained in this release (see the maintenance releases'
57 * "git log --pretty/format=" with an empty format string did not
58 mean the more obvious "No output whatsoever" but "Use default
59 format", which was counterintuitive.
60 (merge b9c7d6e jk/pretty-empty-format later to maint).
62 * Implementations of "tar" that do not understand an extended pax
63 header would extract the contents of it in a regular file; make
64 sure the permission bits of this file follows the same tar.umask
65 configuration setting.
67 * "git -c section.var command" and "git -c section.var= command"
68 should pass the configuration differently (the former should be a
69 boolean true, the latter should be an empty string).
70 (merge a789ca7 jk/command-line-config-empty-string later to maint).
72 * Applying a patch not generated by Git in a subdirectory used to
73 check the whitespace breakage using the attributes for incorrect
74 paths. Also whitespace checks were performed even for paths
75 excluded via "git apply --exclude=<path>" mechanism.
76 (merge 477a08a jc/apply-ws-prefix later to maint).
78 * "git bundle create" with date-range specification were meant to
79 exclude tags outside the range, but it didn't.
80 (merge 2c8544a lf/bundle-exclusion later to maint).
82 * "git add x" where x that used to be a directory has become a
83 symbolic link to a directory misbehaved.
84 (merge ccad42d rs/refresh-beyond-symlink later to maint).
86 * The prompt script checked $GIT_DIR/ref/stash file to see if there
87 is a stash, which was a no-no.
88 (merge 0fa7f01 jk/prompt-stash-could-be-packed later to maint).
90 * Pack-protocol documentation had a minor typo.
91 (merge 5d146f7 sp/pack-protocol-doc-on-shallow later to maint).
projects / thirdparty / git.git / blob