]>
Commit | Line | Data |
---|---|---|
ad12b812 JH |
1 | GIT v1.6.6 Release Notes |
2 | ======================== | |
3 | ||
f29cd393 JH |
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. | |
11 | ||
ad12b812 JH |
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. | |
15 | ||
16 | You can choose what should happen upon such a push by setting the | |
17 | configuration variable receive.denyCurrentBranch in the receiving | |
18 | repository. | |
19 | ||
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. | |
23 | ||
24 | You can choose what should happen upon such a push by setting the | |
25 | configuration variable receive.denyDeleteCurrent in the receiving | |
26 | repository. | |
27 | ||
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: | |
31 | ||
32 | http://git.or.cz/gitwiki/GitFaq#non-bare | |
33 | http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007 | |
34 | ||
35 | for more details on the reason why this change is needed and the | |
36 | transition plan. | |
37 | ||
38 | Updates since v1.6.5 | |
39 | -------------------- | |
40 | ||
41 | (subsystems) | |
42 | ||
43 | (portability) | |
44 | ||
45 | (performance) | |
46 | ||
47 | (usability, bells and whistles) | |
48 | ||
610f99ec JH |
49 | * The object replace mechanism can be bypassed with --no-replace-objects |
50 | global option given to the "git" program. | |
51 | ||
f29cd393 JH |
52 | * "git fsck" by default checks the packfiles (i.e. "--full" is the |
53 | default); you can turn it off with "git fsck --no-full". | |
54 | ||
610f99ec JH |
55 | * import-tars contributed fast-import frontend learned more types of |
56 | compressed tarballs. | |
57 | ||
58 | * "git instaweb" knows how to talk with mod_cgid to apache2. | |
59 | ||
ad12b812 JH |
60 | * "git log --decorate" shows the location of HEAD as well. |
61 | ||
610f99ec JH |
62 | * "git rebase -i" learned "reword" that acts like "edit" but immediately |
63 | starts an editor to tweak the log message without returning control to | |
64 | the shell, which is done by "edit" to give an opportunity to tweak the | |
65 | contents. | |
66 | ||
67 | * Author names shown in gitweb output are links to search commits by the | |
68 | author. | |
69 | ||
70 | ||
ad12b812 JH |
71 | (developers) |
72 | ||
73 | Fixes since v1.6.5 | |
74 | ------------------ | |
75 | ||
76 | All of the fixes in v1.6.5.X maintenance series are included in this | |
77 | release, unless otherwise noted. | |
78 | ||
79 | * "git apply" and "git diff" (including patch output from "git log -p") | |
80 | now flags trailing blank lines as whitespace errors correctly (only | |
81 | "apply --whitespace=fix" stripped them but "apply --whitespace=warn" | |
82 | did not even warn). | |
83 | ||
84 | * Two whitespace error classes, 'blank-at-eof' and 'blank-at-eol', have | |
85 | been introduced (settable by core.whitespace configuration variable and | |
86 | whitespace attribute). The 'trailing-space' whitespace error class has | |
87 | become a short-hand to cover both of these and there is no behaviour | |
88 | change for existing set-ups. | |
610f99ec JH |
89 | |
90 | * "git cvsimport" did not work well when it is fed filenames from the | |
91 | command line and is not started at the top of the work tree. We should | |
92 | backport this by merging f6fdbb6 (cvsimport: fix relative argument | |
93 | filenames, 2009-10-19). | |
94 | ||
95 | * The way gitweb escapes its CGI parameters were broken especially when | |
96 | the parameter was a UTF-8 string. We may want to backport this to | |
97 | 1.6.5.X series by merging 452e225 (gitweb: fix esc_param, 2009-10-13). | |
98 | ||
99 | * gitweb used to show 'patch' link for merge commits but the output from | |
100 | it is not usable to feed "git am" with. We may want to backport this | |
101 | to 1.6.5.X series by merging 1655c98 (gitweb: Do not show 'patch' link | |
102 | for merge commits, 2009-10-09). | |
103 | ||
104 | --- | |
105 | exec >/var/tmp/1 | |
106 | echo O=$(git describe master) | |
107 | O=v1.6.5.2-73-g9b12444 | |
108 | git shortlog --no-merges $O..master --not maint |