| blob | fa0e11a1806793bfef3e03df477f1cc5dbb0800d |
1 GIT v1.6.6 Release Notes
2 ========================
4 In this release, "git fsck" defaults to "git fsck --full" and checks
5 packfiles, and because of this it will take much longer to complete
6 than before. If you prefer a quicker check only on loose objects (the
7 old default), you can say "git fsck --no-full". This has been
8 supported by 1.5.4 and newer versions of git, so it is safe to write
9 it in your script even if you use slightly older git on some of your
10 machines.
12 In git 1.7.0, which is planned to be the release after 1.6.6, "git
13 push" into a branch that is currently checked out will be refused by
14 default.
16 You can choose what should happen upon such a push by setting the
17 configuration variable receive.denyCurrentBranch in the receiving
18 repository.
20 Also, "git push $there :$killed" to delete the branch $killed in a remote
21 repository $there, when $killed branch is the current branch pointed at by
22 its HEAD, will be refused by default.
24 You can choose what should happen upon such a push by setting the
25 configuration variable receive.denyDeleteCurrent in the receiving
26 repository.
28 To ease the transition plan, the receiving repository of such a
29 push running this release will issue a big warning when the
30 configuration variable is missing. Please refer to:
32 http://git.or.cz/gitwiki/GitFaq#non-bare
33 http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
35 for more details on the reason why this change is needed and the
36 transition plan.
38 Updates since v1.6.5
39 --------------------
41 (subsystems)
43 (portability)
45 (performance)
47 (usability, bells and whistles)
49 * "git fsck" by default checks the packfiles (i.e. "--full" is the
50 default); you can turn it off with "git fsck --no-full".
52 * "git log --decorate" shows the location of HEAD as well.
54 (developers)
56 Fixes since v1.6.5
57 ------------------
59 All of the fixes in v1.6.5.X maintenance series are included in this
60 release, unless otherwise noted.
62 * "git apply" and "git diff" (including patch output from "git log -p")
63 now flags trailing blank lines as whitespace errors correctly (only
64 "apply --whitespace=fix" stripped them but "apply --whitespace=warn"
65 did not even warn).
67 * Two whitespace error classes, 'blank-at-eof' and 'blank-at-eol', have
68 been introduced (settable by core.whitespace configuration variable and
69 whitespace attribute). The 'trailing-space' whitespace error class has
70 become a short-hand to cover both of these and there is no behaviour
71 change for existing set-ups.