| blob | dcef36e671d91b6f2e9abd3c5c2b744c2a1fb822 |
1 Git v1.8.3 Release Notes
2 ========================
4 Backward compatibility notes (for Git 2.0)
5 ------------------------------------------
7 When "git push [$there]" does not say what to push, we have used the
8 traditional "matching" semantics so far (all your branches were sent
9 to the remote as long as there already are branches of the same name
10 over there). In Git 2.0, the default will change to the "simple"
11 semantics that pushes the current branch to the branch with the same
12 name, only when the current branch is set to integrate with that
13 remote branch. There is a user preference configuration variable
14 "push.default" to change this. If you are an old-timer who is used
15 to the "matching" semantics, you can set it to "matching" to keep the
16 traditional behaviour. If you want to live in the future early,
17 you can set it to "simple" today without waiting for Git 2.0.
19 When "git add -u" and "git add -A", that does not specify what paths
20 to add on the command line is run from inside a subdirectory, these
21 commands will operate on the entire tree in Git 2.0 for consistency
22 with "git commit -a" and other commands. Because there will be no
23 mechanism to make "git add -u" behave as if "git add -u .", it is
24 important for those who are used to "git add -u" (without pathspec)
25 updating the index only for paths in the current subdirectory to start
26 training their fingers to explicitly say "git add -u ." when they mean
27 it before Git 2.0 comes.
30 Updates since v1.8.2
31 --------------------
33 UI, Workflows & Features
35 * When the interactive access to git-shell is not enabled, it issues
36 a message meant to help the system admininstrator to enable it.
37 An explicit way to help the end users who connect to the service by
38 issuing custom messages to refuse such an access has been added.
40 * In addition to the case where the user edits the log message with
41 the "e)dit" option of "am -i", replace the "Applying: this patch"
42 message with the final log message contents after applymsg hook
43 munges it.
45 * "git status" suggests users to look into using --untracked=no option
46 when it takes too long.
48 * "git status" shows a bit more information to "git status" during a
49 rebase/bisect session.
51 * "git fetch" learned to fetch a commit at the tip of an unadvertised
52 ref by specifying a raw object name from the command line when the
53 server side supports this feature.
55 * "git count-objects -v" learned to report leftover temporary
56 packfiles and other garbage in the object store.
58 * A new read-only credential helper (in contrib/) to interact with
59 the .netrc/.authinfo files has been added.
61 * "git send-email" can be used with the credential helper system.
63 * There was no Porcelain way to say "I no longer am interested in
64 this submodule", once you express your interest in a submodule with
65 "submodule init". "submodule deinit" is the way to do so.
67 * "git pull --rebase" learned to pass "-v/-q" options to underlying
68 "git rebase".
70 * The new "--follow-tags" option tells "git push" to push relevant
71 annotated tags when pushing branches out.
73 * "git mergetool" now feeds files to the "p4merge" backend in the
74 order that matches the p4 convention, where "theirs" is usually
75 shown on the left side, which is the opposite from other backend
76 expects.
79 Performance, Internal Implementation, etc.
81 * Updates for building under msvc.
83 * A few codepaths knew how much data they need to put in the
84 hashtables they use upfront, but still started from a small table
85 repeatedly growing and rehashing.
87 * The API to walk reflog entries from the latest to older, which was
88 necessary for operations such as "git checkout -", was cumbersome
89 to use correctly and also inefficient.
91 * Codepaths that inspect log-message-to-be and decide when to add a
92 new Signed-off-by line in various commands have been consolidated.
94 * The pkt-line API, implementation and its callers have been cleaned
95 up to make them more robust.
98 Also contains minor documentation updates and code clean-ups.
101 Fixes since v1.8.2
102 ------------------
104 Unless otherwise noted, all the fixes since v1.8.2 in the maintenance
105 track are contained in this release (see release notes to them for
106 details).
108 * "index-pack --fix-thin" used uninitialize value to compute delta
109 depths of objects it appends to the resulting pack.
110 (merge 57165db jk/index-pack-correct-depth-fix later to maint).
112 * "index-pack --verify-stat" used a few counters outside protection
113 of mutex, possibly showing incorrect numbers.
114 (merge 8f82aad nd/index-pack-threaded-fixes later to maint).
116 * The code to keep track of what directory names are known to Git on
117 platforms with case insensitive filesystems can get confused upon a
118 hash collision between these pathnames and looped forever.
119 (merge 2092678 kb/name-hash later to maint).
121 * Annotated tags outside refs/tags/ hierarchy were not advertised
122 correctly to the ls-remote and fetch with recent version of Git.
123 (merge c29c46f jk/fully-peeled-packed-ref later to maint).
125 * Recent optimization broke shallow clones.
126 (merge f59de5d jk/peel-ref later to maint).
128 * "git cmd -- ':(top'" was not diagnosed as an invalid syntax, and
129 instead the parser kept reading beyond the end of the string.
130 (merge f612a67 lf/setup-prefix-pathspec later to maint).
132 * "git tag -f <tag>" always said "Updated tag '<tag>'" even when
133 creating a new tag (i.e. not overwriting nor updating).
134 (merge 3ae851e ph/tag-force-no-warn-on-creation later to maint).
136 * "git p4" did not behave well when the path to the root of the P4
137 client was not its real path.
138 (merge bbd8486 pw/p4-symlinked-root later to maint).
140 * "git archive" reports a failure when asked to create an archive out
141 of an empty tree. It would be more intuitive to give an empty
142 archive back in such a case.
143 (merge bd54cf1 jk/empty-archive later to maint).
145 * When "format-patch" quoted a non-ascii strings on the header files,
146 it incorrectly applied rfc2047 and chopped a single character in
147 the middle of it.
148 (merge 6cd3c05 ks/rfc2047-one-char-at-a-time later to maint).
150 * An aliased command spawned from a bare repository that does not say
151 it is bare with "core.bare = yes" is treated as non-bare by mistake.
152 (merge 2cd83d1 jk/alias-in-bare later to maint).
154 * In "git reflog expire", REACHABLE bit was not cleared from the
155 correct objects.
157 * The logic used by "git diff -M --stat" to shorten the names of
158 files before and after a rename did not work correctly when the
159 common prefix and suffix between the two filenames overlapped.
161 * The "--match=<pattern>" option of "git describe", when used with
162 "--all" to allow refs that are not annotated tags to be used as a
163 base of description, did not restrict the output from the command
164 to those that match the given pattern.
165 (merge 46e1d6e jc/describe later to maint).
167 * Clarify in the documentation "what" gets pushed to "where" when the
168 command line to "git push" does not say these explicitly.
170 * The "--color=<when>" argument to the commands in the diff family
171 was described poorly.
173 * The arguments given to pre-rebase hook were not documented.
175 * The v4 index format was not documented.
177 * The "--match=<pattern>" argument "git describe" takes uses glob
178 pattern but it wasn't obvious from the documentation.
180 * Some sources failed to compile on systems that lack NI_MAXHOST in
181 their system header (e.g. z/OS).
183 * Add an example use of "--env-filter" in "filter-branch"
184 documentation.
186 * "git bundle verify" did not say "records a complete history" for a
187 bundle that does not have any prerequisites.
189 * In the v1.8.0 era, we changed symbols that do not have to be global
190 to file scope static, but a few functions in graph.c were used by
191 CGit from sideways bypassing the entry points of the API the
192 in-tree users use.
194 * "git update-index -h" did not do the usual "-h(elp)" thing.
196 * "git index-pack" had a buffer-overflow while preparing an
197 informational message when the translated version of it was too
198 long.
200 * 'git commit -m "$msg"' used to add an extra newline even when
201 $msg already ended with one.
202 (merge 46fbf75 bc/commit-complete-lines-given-via-m-option later to maint).
204 * The SSL peer verification done by "git imap-send" did not ask for
205 Server Name Indication (RFC 4366), failing to connect SSL/TLS
206 sites that serve multiple hostnames on a single IP.
208 * perl/Git.pm::cat_blob slurped everything in core only to write it
209 out to a file descriptor, which was not a very smart thing to do.
211 * "git branch" did not bother to check nonsense command line
212 parameters and issue errors in many cases.
214 * Verification of signed tags were not done correctly when not in C
215 or en/US locale.
216 (merge 0174eea mg/gpg-interface-using-status later to maint).
218 * Some platforms and users spell UTF-8 differently; retry with the
219 most official "UTF-8" when the system does not understand the
220 user-supplied encoding name that are the common alternative
221 spellings of UTF-8.
223 * When export-subst is used, "zip" output recorded incorrect
224 size of the file.
226 * "git am $maildir/" applied messages in an unexpected order; sort
227 filenames read from the maildir/ in a way that is more likely to
228 sort messages in the order the writing MUA meant to, by sorting
229 numeric segment in numeric order and non-numeric segment in
230 alphabetical order.
232 * "git submodule update", when recursed into sub-submodules, did not
233 acccumulate the prefix paths.