Junio C Hamano <gits...@pobox.com> writes: >> I don't understand: wasn't this supposed to happen in Git 2.0? Did you >> mean "In the upcoming major release (tentatively called *2.0*)"? > > Thanks. I am not sure what I was thinking. Perhaps when we started > this cycle we did want to merge the push-2.0-default-to-simple series > > Will update. > >> Also, you may want to mention the argumentless "git add -u" change too. >> It currently has an item below, but this is a future >> backward-incompatible change so it may deserve to appear in this section >> too.
OK, let's do this. Thanks for sharp eyes. Documentation/RelNotes/1.8.2.txt | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/Documentation/RelNotes/1.8.2.txt b/Documentation/RelNotes/1.8.2.txt index a5a1d4e..a287f24 100644 --- a/Documentation/RelNotes/1.8.2.txt +++ b/Documentation/RelNotes/1.8.2.txt @@ -4,8 +4,8 @@ Git v1.8.2 Release Notes Backward compatibility notes ---------------------------- -In the upcoming major release (tentatively called 1.8.2), we will -change the behavior of the "git push" command. +In the next major release Git 2.0 (not *this* one), we will change the +behavior of the "git push" command. When "git push [$there]" does not say what to push, we have used the 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 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 -------------------- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html