| blob | 90c4f4795fc5e95292d42dde52a7b41b0b76387d |
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 * A credential helper to allow access to the Gnome keyring has been
32 added.
34 * When "git am" sanitizes the Subject: line, we strip the prefix from
35 "Re: subject" and also from a less common "re: subject", but left
36 even less common "RE: subject" intact.
38 * It was tempting to say "git branch --set-upstream origin/master",
39 but that tells Git to arrange the local branch "origin/master" to
40 integrate with the currently checked out branch, which is highly
41 unlikely what the user meant. The option is deprecated; use the
42 new "--set-upstream-to" (with a short-and-sweet "-u") option
43 instead.
45 * "git cherry-pick" learned the "--allow-empty-message" option to
46 allow it to replay a commit without any log message.
48 * "git daemon" learned the "--access-hook" option to allow an
49 external command to decline service based on the client address,
50 repository path, etc.
52 * "git difftool --dir-diff" learned to use symbolic links to prepare
53 temporary copy of the working tree when available.
55 * "git grep" learned to use a non-standard pattern type by default if
56 a configuration variable tells it to.
58 * "git merge-base" learned "--is-ancestor A B" option to tell if A is
59 an ancestor of B. The result is indicated by its exit status code.
61 * The "-Xours" backend option to "git merge -s recursive" now takes
62 effect even on binary files.
65 Foreign Interface
67 * "git svn" has been updated to work with SVN 1.7.
70 Performance, Internal Implementation, etc. (please report possible regressions)
72 * Git ships with a fall-back regexp implementation for platforms with
73 buggy regexp library, but it was easy for people to keep using their
74 platform regexp. A new test has been added to check this.
76 * The "check-docs" build target has been updated and greatly
77 simplified.
79 * The documentation in the TeXinfo format was using indented output
80 for materials meant to be examples that are better typeset in
81 monospace.
83 * Compatibility wrapper around some mkdir(2) implementations that
84 reject parameter with trailing slash has been introduced.
86 * Compatibility wrapper for systems that lack usable setitimer() has
87 been added.
89 * The option parsing of "git checkout" had error checking, dwim and
90 defaulting missing options, all mixed in the code, and issuing an
91 appropriate error message with useful context was getting harder.
92 The code has been reorganized to allow giving a proper diagnosis
93 when the user says "git checkout -b -t foo bar" (e.g. "-t" is not a
94 good name for a branch).
96 * Many internal uses of "git merge-base" equivalent were only to see
97 if one commit fast-forwards to the other, which did not need the
98 full set of merge bases to be computed. They have been updated to
99 use less expensive checks.
101 * The heuristics to detect and silently convert latin1 to utf8 when
102 we were told to use utf-8 in the log message has been transplanted
103 from "mailinfo" to "commit" and "commit-tree".
105 * Messages given by "git <subcommand> -h" from many subcommands have
106 been marked for translation.
109 Also contains minor documentation updates and code clean-ups.
112 Fixes since v1.7.12
113 -------------------
115 Unless otherwise noted, all the fixes since v1.7.12 in the
116 maintenance track are contained in this release (see release notes
117 to them for details).
119 * "git fetch --all", when passed "--no-tags", did not honor the
120 "--no-tags" option while fetching from individual remotes (the same
121 issue existed with "--tags", but combination "--all --tags" makes
122 much less sense than "--all --no-tags").
123 (merge 8556646 dj/fetch-all-tags later to maint).
125 * The subcommand in "git remote" to remove a defined remote was
126 "rm" and the command did not take a fully-spelled "remove".
127 (merge e17dba8 nd/maint-remote-remove later to maint).
129 * After "gitk" showed the contents of a tag, neither "Reread
130 references" nor "Reload" did not update what is shown as the
131 contents of it, when the user overwrote the tag with "git tag -f".
133 * "git cvsimport" did not thoroughly cleanse tag names that it
134 inferred from the names of the tags it obtained from CVS, which
135 caused "git tag" to barf and stop the import in the middle.
137 * "git show --format='%ci'" did not give timestamp correctly for
138 commits created without human readable name on "committer" line.
139 (merge e27ddb6 jc/maint-ident-missing-human-name later to maint).
141 * "git cherry-pick A C B" used to replay changes in A and then B and
142 then C if these three commits had committer timestamps in that
143 order, which is not what the user who said "A C B" naturally
144 expects.
145 (merge a73e22e mz/cherry-pick-cmdline-order later to maint).
147 * "git show --quiet" ought to be a synonym for "git show -s", but
148 wasn't.
149 (merge f9c75d8 jk/maint-quiet-is-synonym-to-s-in-log later to maint).
151 * "git p4", when "--use-client-spec" and "--detect-branches" are used
152 together, misdetected branches.
153 (merge 21ef5df pw/p4-use-client-spec-branch-detection later to maint).
155 * Output from "git branch -v" contains "(no branch)" that could be
156 localized, but the code to align it along with the names of
157 branches were counting in bytes, not in display columns.
158 (merge 1452bd6 nd/branch-v-alignment later to maint).
160 * When looking for $HOME/.gitconfig etc., it is OK if we cannot read
161 them because they do not exist, but we did not diagnose existing
162 files that we cannot read.
164 * The interactive prompt "git send-email" gives was error prone. It
165 asked "What e-mail address do you want to use?" with the address it
166 guessed (correctly) the user would want to use in its prompt,
167 tempting the user to say "y". But the response was taken as "No,
168 please use 'y' as the e-mail address instead", which is most
169 certainly not what the user meant.
170 (merge 6183749 sb/send-email-reconfirm-fix later to maint).