@@ -4,16 +4,18 @@ Git v1.8.0 Release Notes
4
4
Backward compatibility notes
5
5
----------------------------
6
6
7
- In the next major release, we will change the behavior of the "git
8
- push" command. When "git push [$there]" does not say what to push, we
9
- have used the traditional "matching" semantics so far (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 now use the "simple" semantics, that pushes the
12
- current branch to the branch with the same name only when the current
7
+ In the next major release (not *this* one), we will change the
8
+ behavior of the "git push" command.
9
+
10
+ When "git push [$there]" does not say what to push, we have used the
11
+ traditional "matching" semantics so far (all your branches were sent
12
+ to the remote as long as there already are branches of the same name
13
+ over there). We will use the "simple" semantics that pushes the
14
+ current branch to the branch with the same name, only when the current
13
15
branch is set to integrate with that remote branch. There is a user
14
16
preference configuration variable "push.default" to change this, and
15
17
"git push" will warn about the upcoming change until you set this
16
- variable.
18
+ variable in this release .
17
19
18
20
"git branch --set-upstream" is deprecated and may be removed in a
19
21
relatively distant future. "git branch [-u|--set-upstream-to]" has
@@ -35,7 +37,7 @@ UI, Workflows & Features
35
37
36
38
* When "git am" sanitizes the "Subject:" line, we strip the prefix from
37
39
"Re: subject" and also from a less common "re: subject", but left
38
- the even less common "RE: subject" intact. We strip that now, too.
40
+ the even less common "RE: subject" intact. Now we strip that too.
39
41
40
42
* It was tempting to say "git branch --set-upstream origin/master",
41
43
but that tells Git to arrange the local branch "origin/master" to
@@ -62,6 +64,8 @@ UI, Workflows & Features
62
64
* "git grep" learned to use a non-standard pattern type by default if
63
65
a configuration variable tells it to.
64
66
67
+ * Accumulated updates to "git gui" has been merged.
68
+
65
69
* "git log -g" learned the "--grep-reflog=<pattern>" option to limit
66
70
its output to commits with a reflog message that matches the given
67
71
pattern.
@@ -85,7 +89,7 @@ Foreign Interface
85
89
encountering a conflict during "p4 submit".
86
90
87
91
88
- Performance, Internal Implementation, etc. (please report possible regressions)
92
+ Performance, Internal Implementation, etc.
89
93
90
94
* Git ships with a fall-back regexp implementation for platforms with
91
95
buggy regexp library, but it was easy for people to keep using their
0 commit comments