| blob | e183df6410ecf1242636d58f3e2bd579108b6241 |
1 Git v1.8.0 Release Notes
2 ========================
4 Backward compatibility notes
5 ----------------------------
7 In the next major release, we will change the behaviour of the "git
8 push" command. When "git push [$there]" does not say what to push, we
9 have used the traditional "matching" semantics (all your branches were
10 sent to the remote as long as there already are branches of the same
11 name over there). We will use the "simple" semantics, that pushes the
12 current branch to the branch with the same name only when the current
13 branch is set to integrate with that remote branch. There is a user
14 preference configuration variable "push.default" to change this, and
15 "git push" will warn about the upcoming change until you set this
16 variable.
18 "git branch --set-upstream" is deprecated and may be removed in a
19 relatively distant future. "git branch [-u|--set-upstream-to]" has
20 been introduced with a saner order of arguments.
23 Updates since v1.7.12
24 ---------------------
26 UI, Workflows & Features
28 * A credential helper for Win32 to allow access to the keychain of
29 the logged-in user has been added.
31 * An initial port to HP NonStop.
33 * A credential helper to allow access to the Gnome keyring has been
34 added.
36 * When "git am" sanitizes the Subject: line, we strip the prefix from
37 "Re: subject" and also from a less common "re: subject", but left
38 even less common "RE: subject" intact.
40 * It was tempting to say "git branch --set-upstream origin/master",
41 but that tells Git to arrange the local branch "origin/master" to
42 integrate with the currently checked out branch, which is highly
43 unlikely what the user meant. The option is deprecated; use the
44 new "--set-upstream-to" (with a short-and-sweet "-u") option
45 instead.
47 * "git cherry-pick" learned the "--allow-empty-message" option to
48 allow it to replay a commit without any log message.
50 * After "git cherry-pick -s" gave control back to the user asking
51 help to resolve conflicts, concluding "git commit" used to need to
52 be run with "-s" if the user wants to sign it off; now the command
53 leaves the sign-off line in the log template.
55 * "git daemon" learned the "--access-hook" option to allow an
56 external command to decline service based on the client address,
57 repository path, etc.
59 * "git difftool --dir-diff" learned to use symbolic links to prepare
60 temporary copy of the working tree when available.
62 * "git grep" learned to use a non-standard pattern type by default if
63 a configuration variable tells it to.
65 * "git merge-base" learned "--is-ancestor A B" option to tell if A is
66 an ancestor of B. The result is indicated by its exit status code.
68 * The "-Xours" backend option to "git merge -s recursive" now takes
69 effect even on binary files.
71 * "git rebase -i" learned the "--edit-todo" option to open an editor
72 to edit the insn sheet.
75 Foreign Interface
77 * "git svn" has been updated to work with SVN 1.7.
79 * "git p4" learned "--conflicts" option to specify what to do when
80 encountering a conflict during "p4 submit".
83 Performance, Internal Implementation, etc. (please report possible regressions)
85 * Git ships with a fall-back regexp implementation for platforms with
86 buggy regexp library, but it was easy for people to keep using their
87 platform regexp. A new test has been added to check this.
89 * The "check-docs" build target has been updated and greatly
90 simplified.
92 * The test suite is run under MALLOC_CHECK_ when running with glibc
93 that supports the feature.
95 * The documentation in the TeXinfo format was using indented output
96 for materials meant to be examples that are better typeset in
97 monospace.
99 * Compatibility wrapper around some mkdir(2) implementations that
100 reject parameter with trailing slash has been introduced.
102 * Compatibility wrapper for systems that lack usable setitimer() has
103 been added.
105 * The option parsing of "git checkout" had error checking, dwim and
106 defaulting missing options, all mixed in the code, and issuing an
107 appropriate error message with useful context was getting harder.
108 The code has been reorganized to allow giving a proper diagnosis
109 when the user says "git checkout -b -t foo bar" (e.g. "-t" is not a
110 good name for a branch).
112 * Many internal uses of "git merge-base" equivalent were only to see
113 if one commit fast-forwards to the other, which did not need the
114 full set of merge bases to be computed. They have been updated to
115 use less expensive checks.
117 * The heuristics to detect and silently convert latin1 to utf8 when
118 we were told to use utf-8 in the log message has been transplanted
119 from "mailinfo" to "commit" and "commit-tree".
121 * Messages given by "git <subcommand> -h" from many subcommands have
122 been marked for translation.
125 Also contains minor documentation updates and code clean-ups.
128 Fixes since v1.7.12
129 -------------------
131 Unless otherwise noted, all the fixes since v1.7.12 in the
132 maintenance track are contained in this release (see release notes
133 to them for details).
135 * The attribute system may be asked for a path that itself or its
136 leading directories no longer exists in the working tree, and it is
137 fine if we cannot open .gitattribute file in such a case. Failure
138 to open per-directory .gitattributes with error status other than
139 ENOENT and ENOTDIR should be diagnosed, but it wasn't.
141 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read
142 them because they do not exist, but we did not diagnose existing
143 files that we cannot read.
145 * When "git am" is fed an input that has multiple "Content-type: ..."
146 header, it did not grok charset= attribute correctly.
148 * "git blame MAKEFILE" run in a history that has "Makefile" but not
149 "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
150 confused on a case insensitive filesystem and failed to do so.
152 * Even during a conflicted merge, "git blame $path" always meant to
153 blame uncommitted changes to the "working tree" version; make it
154 more useful by showing cleanly merged parts as coming from the other
155 branch that is being merged.
157 * Output from "git branch -v" contains "(no branch)" that could be
158 localized, but the code to align it along with the names of
159 branches were counting in bytes, not in display columns.
161 * "git cherry-pick A C B" used to replay changes in A and then B and
162 then C if these three commits had committer timestamps in that
163 order, which is not what the user who said "A C B" naturally
164 expects.
166 * Documentation talked about "first line of commit log" when it meant
167 the title of the commit. The description was clarified by defining
168 how the title is decided and rewording the casual mention of "first
169 line" to "title".
171 * "git cvsimport" did not thoroughly cleanse tag names that it
172 inferred from the names of the tags it obtained from CVS, which
173 caused "git tag" to barf and stop the import in the middle.
175 * Earlier we made the diffstat summary line that shows the number of
176 lines added/deleted localizable, but it was found irritating having
177 to see them in various languages on a list whose discussion language
178 is English.
180 * "git fetch --all", when passed "--no-tags", did not honor the
181 "--no-tags" option while fetching from individual remotes (the same
182 issue existed with "--tags", but combination "--all --tags" makes
183 much less sense than "--all --no-tags").
185 * "git fetch" over http had an old workaround for an unlikely server
186 misconfiguration; it turns out that this hurts debuggability of the
187 configuration in general, and has been reverted.
188 (merge 6ac964a sp/maint-http-info-refs-no-retry later to maint).
190 * "git fetch" over http advertised that it supports "deflate", which
191 is much less common, and did not advertise more common "gzip" on
192 its Accept-Encoding header.
193 (merge aa90b96 sp/maint-http-enable-gzip later to maint).
195 * After "gitk" showed the contents of a tag, neither "Reread
196 references" nor "Reload" did not update what is shown as the
197 contents of it, when the user overwrote the tag with "git tag -f".
199 * "git log --all-match --grep=A --grep=B" ought to show commits that
200 mention both A and B, but when these three options are used with
201 --author or --committer, it showed commits that mention either A or
202 B (or both) instead.
204 * "git p4", when "--use-client-spec" and "--detect-branches" are used
205 together, misdetected branches.
207 * When you misspell the command name you give to the "exec" action in
208 the "git rebase -i" insn sheet, you are told that 'rebase' is not a
209 git subcommand from "git rebase --continue".
211 * The subcommand in "git remote" to remove a defined remote was
212 "rm" and the command did not take a fully-spelled "remove".
214 * The interactive prompt "git send-email" gives was error prone. It
215 asked "What e-mail address do you want to use?" with the address it
216 guessed (correctly) the user would want to use in its prompt,
217 tempting the user to say "y". But the response was taken as "No,
218 please use 'y' as the e-mail address instead", which is most
219 certainly not what the user meant.
221 * "git show --format='%ci'" did not give timestamp correctly for
222 commits created without human readable name on "committer" line.
224 * "git show --quiet" ought to be a synonym for "git show -s", but
225 wasn't.
227 * "git submodule frotz" was not diagnosed as "frotz" being an unknown
228 subcommand to "git submodule"; the user instead got a complaint
229 that "git submodule status" was run with an unknown path "frotz".
230 (merge af9c9f9 rr/maint-submodule-unknown-cmd later to maint).