undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

RelNotes 1.8.2: push-simple will not be in effect in this release

Browse Source 
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>
This commit is contained in:
Junio C Hamano 2013-02-18 15:59:33 -08:00
parent 31e6a4e613
commit ce209d0c72
1 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/RelNotes/1.8.2.txt
View File

@ -4,8 +4,8 @@ Git v1.8.2 Release Notes
Backward compatibility notes Backward compatibility notes
---------------------------- ----------------------------
In the upcoming major release (tentatively called 1.8.2), we will In the next major release Git 2.0 (not *this* one), we will change the
change the behavior of the "git push" command. behavior of the "git push" command.
When "git push [$there]" does not say what to push, we have used the When "git push [$there]" does not say what to push, we have used the
traditional "matching" semantics so far (all your branches were sent 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
and starting with this release, any attempt to update an existing and starting with this release, any attempt to update an existing
ref under refs/tags/ hierarchy will fail, without "--force". ref under refs/tags/ hierarchy will fail, without "--force".
When "git add -u" and "git add -A", that does not specify what paths
to add on the command line, is run from inside a subdirectory, the
scope of the operation has always been limited to the subirectory.
Many users found this counter-intuitive, given that "git commit -a"
and other commands operate on the entire tree regardless of where you
are. In this release, these commands give warning in such a case and
encourage the user to say "git add -u/-A ." instead when restricting
the scope to the current directory. At Git 2.0 (not *this* one), we
plan to change these commands without pathspec to operate on the
entire tree, and training your fingers to type "." will protect you
against the future change.
Updates since v1.8.1 Updates since v1.8.1
-------------------- --------------------