RelNotes 1.8.2: push-simple will not be in effect in this release
Also migration path for the default behaviour of "git add -u/-A" run in a subdirectory is worth mentioning. Both pointed out by Matthieu Moy. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Feb 18, 2013 at 15:59 UTC
ce209d0c72677cce41c61bfc30a82f468df804ed
1 file changed
+14
-2
Documentation/RelNotes/1.8.2.txt
+14
-2
@@ -4,8 +4,8 @@ Git v1.8.2 Release Notes
4
Backward compatibility notes
5
----------------------------
6
7
-In the upcoming major release (tentatively called 1.8.2), we will
8
-change the behavior of the "git push" command.
7
+In the next major release Git 2.0 (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
@@ -22,6 +22,18 @@ that the old tag v1.2.3 points at. This was found to be error prone
22
and starting with this release, any attempt to update an existing
23
ref under refs/tags/ hierarchy will fail, without "--force".
24
25
+When "git add -u" and "git add -A", that does not specify what paths
26
+to add on the command line, is run from inside a subdirectory, the
27
+scope of the operation has always been limited to the subirectory.
28
+Many users found this counter-intuitive, given that "git commit -a"
29
+and other commands operate on the entire tree regardless of where you
30
+are. In this release, these commands give warning in such a case and
31
+encourage the user to say "git add -u/-A ." instead when restricting
32
+the scope to the current directory. At Git 2.0 (not *this* one), we
33
+plan to change these commands without pathspec to operate on the
34
+entire tree, and training your fingers to type "." will protect you
35
+against the future change.
36
+
37
38
Updates since v1.8.1
39
--------------------