1 Git v1.8.4 Release Notes
2 ========================
9 * Remote transport helper has been updated to report errors and
10 maintain ref hierarchy used to keep track of its own state better.
13 UI, Workflows & Features
15 * "check-ignore" (new feature since 1.8.2) has been updated to work
16 more like "check-attr" over bidi-pipes.
18 * "git describe" learned "--first-parent" option to limit its closest
19 tagged commmit search to the first-parent chain.
21 * "git merge foo" that might have meant "git merge origin/foo" is
22 diagnosed with a more informative error message.
24 * "git log -L<line>,<range>:<filename>" has been added. This may
25 still have leaks and rough edges, though.
27 * We used the approxidate() parser for "--expire=<timestamp>" options
28 of various commands, but it is better to treat --expire=all and
29 --expire=now a bit more specially than using the current timestamp.
30 "git gc" and "git reflog" have been updated with a new parsing
31 function for expiry dates.
33 * Updates to completion (both bash and zsh) helpers.
35 * "git fetch origin master" unlike "git fetch origin" or "git fetch"
36 did not update "refs/remotes/origin/master"; this was an early
37 design decision to keep the update of remote tracking branches
38 predictable, but in practice it turns out that people find it more
39 convenient to opportunisticly update them whenever we have a
40 chance, and we have been updating them when we run "git push" which
41 already breaks the original "predictability" anyway.
44 Performance, Internal Implementation, etc.
46 * The codepath to read from marks files in fast-import/export did not
47 have to accept anything but 40-hex representation of the object
48 name. Further, fast-export did not need full in-core object
49 representation to have parsed wen reading from them. These
50 codepaths have been optimized by taking advantage of these access
53 * Object lookup logic, when the object hashtable starts to become
54 crowded, has been optimized.
56 * When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat
57 inconsistently between the test framework and t/Makefile, and logic
58 to summarize the results looked at a wrong place.
60 * Many warnings from sparse source checker in compat/ area has been
63 * The code to reading and updating packed-refs file has been updated,
64 correcting corner case bugs.
67 Also contains various documentation updates and code clean-ups.
73 Unless otherwise noted, all the fixes since v1.8.3 in the maintenance
74 track are contained in this release (see release notes to them for
77 * "git merge @{-1}~22" was rewritten to "git merge frotz@{1}~22"
78 incorrectly when your previous branch was "frotz" (it should be
79 rewritten to "git merge frotz~22" instead).
80 (merge 84cf246 jc/strbuf-branchname-fix later to maint).
82 * "git diff -c -p" was not showing a deleted line from a hunk when
83 another hunk immediately begins where the earlier one ends.
84 (merge aac3857 mk/combine-diff-context-horizon-fix later to maint).
86 * "git log --ancestry-path A...B" did not work as expected, as it did
87 not pay attention to the fact that the merge base between A and B
88 was the bottom of the range being specified.
89 (merge a765499 kb/ancestry-path-threedots later to maint).
91 * Mac OS X does not like to write(2) more than INT_MAX number of
92 bytes; work it around by chopping write(2) into smaller pieces.
93 (merge 6c642a8 fc/macos-x-clipped-write later to maint).
95 * Newer MacOS X encourages the programs to compile and link with
96 their CommonCrypto, not with OpenSSL.
97 (merge be4c828 da/darwin later to maint).
99 * "git clone foo/bar:baz" cannot be a request to clone from a remote
100 over git-over-ssh specified in the scp style. This case is now
101 detected and clones from a local repository at "foo/bar:baz".
102 (merge 6000334 nd/clone-local-with-colon later to maint).
104 * When $HOME is misconfigured to point at an unreadable directory, we
105 used to complain and die. Loosen the check.
106 (merge 4698c8f jn/config-ignore-inaccessible later to maint).
108 * "git subtree" (in contrib/) had one codepath with loose error
109 checks to lose data at the remote side.
110 (merge 3212d56 jk/subtree-do-not-push-if-split-fails later to maint).
112 * "git fetch" into a shallow repository from a repository that does
113 not know about the shallow boundary commits (e.g. a different fork
114 from the repository the current shallow repository was cloned from)
115 did not work correctly.
116 (merge 71d5f93 mh/fetch-into-shallow later to maint).
118 * "git checkout foo" DWIMs the intended "upstream" and turns it into
119 "git checkout -t -b foo remotes/origin/foo". This codepath has been
120 updated to correctly take existing remote definitions into account.
121 (merge 229177a jh/checkout-auto-tracking later to maint).