Start the post 1.8.2 cycle
Again, tentatively let's call this cycle 1.8.3. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 18, 2013 at 15:01 UTC
048d4d98b35e78c44d93b8009f7b11823660e007
3 files changed
+55
-2
Documentation/RelNotes/1.8.3.txt
new
+53
@@ -0,0 +1,53 @@
1
+Git v1.8.3 Release Notes
2
+========================
3
+
4
+Backward compatibility notes (for Git 2.0)
5
+------------------------------------------
6
+
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.
18
+
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.
28
+
29
+
30
+Updates since v1.8.2
31
+--------------------
32
+
33
+UI, Workflows & Features
34
+
35
+
36
+
37
+Foreign Interface
38
+
39
+
40
+
41
+Performance, Internal Implementation, etc.
42
+
43
+
44
+
45
+Also contains minor documentation updates and code clean-ups.
46
+
47
+
48
+Fixes since v1.8.2
49
+------------------
50
+
51
+Unless otherwise noted, all the fixes since v1.8.2 in the maintenance
52
+track are contained in this release (see release notes to them for
53
+details).
GIT-VERSION-GEN
+1
-1
@@ -1,7 +1,7 @@
1
#!/bin/sh
2
3
GVF=GIT-VERSION-FILE
4
-DEF_VER=v1.8.2
4
+DEF_VER=v1.8.2.GIT
5
6
LF='
7
'
RelNotes
+1
-1
@@ -1 +1 @@
1
-Documentation/RelNotes/1.8.2.txt
\ No newline at end of file
1
+Documentation/RelNotes/1.8.3.txt
\ No newline at end of file