GIT 1.5.2.2
[git/git.git] / Documentation / RelNotes-1.5.2.2.txt
1 GIT v1.5.2.2 Release Notes
2 ==========================
3
4 Fixes since v1.5.2.1
5 --------------------
6
7 * Usability fix
8
9 - git-gui is shipped with its updated blame interface. It is
10 rumored that the older one was not just unusable but was
11 active health hazard, but this one is actually pretty.
12 Please see for yourself.
13
14 * Bugfixes
15
16 - "git checkout fubar" was utterly confused when there is a
17 branch fubar and a tag fubar at the same time. It correctly
18 checks out the branch fubar now.
19
20 - "git clone /path/foo" to clone a local /path/foo.git
21 repository left an incorrect configuration.
22
23 - "git send-email" correctly unquotes RFC 2047 quoted names in
24 the patch-email before using their values.
25
26 - We did not accept number of seconds since epoch older than
27 year 2000 as a valid timestamp. We now interpret positive
28 integers more than 8 digits as such, which allows us to
29 express timestamps more recent than March 1973.
30
31 - git-cvsimport did not work when you have GIT_DIR to point
32 your repository at a nonstandard location.
33
34 - Some systems (notably, Solaris) lack hstrerror() to make
35 h_errno human readable; prepare a replacement
36 implementation.
37
38 - .gitignore file listed git-core.spec but what we generate is
39 git.spec, and nobody noticed for a long time.
40
41 - "git-merge-recursive" does not try to run file level merge
42 on binary files.
43
44 - "git-branch --track" did not create tracking configuration
45 correctly when the branch name had slash in it.
46
47 - The email address of the user specified with user.email
48 configuration was overriden by EMAIL environment variable.
49
50 - The tree parser did not warn about tree entries with
51 nonsense file modes, and assumed they must be blobs.
52
53 - "git log -z" without any other request to generate diff still
54 invoked the diff machinery, wasting cycles.
55
56 * Documentation
57
58 - Many updates to fix stale or missing documentation.
59
60 - Although our documentation was primarily meant to be formatted
61 with AsciiDoc7, formatting with AsciiDoc8 is supported better.