Re: push.default: current vs upstream
In the meantime, we can do this.
Documentation/RelNotes/1.7.10.txt | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/Documentation/RelNotes/1.7.10.txt b/Documentation/RelNotes/1.7.10.txt
index d326ff8..6dcaf45 100644
--- a/Documentation/RelNotes/1.7.10.txt
+++ b/Documentation/RelNotes/1.7.10.txt
@@ -32,12 +32,9 @@ Compatibility Notes
* When you do not tell which branches and tags to push to the "git push"
command in any way, the command used "matching refs" rule to update
remote branches and tags with branches and tags with the same name you
- locally have. In future versions of Git, this will change to use the
- "upstream" rule to update the branch at the remote you would "pull"
- from into your current branch with your local current branch. The
- release after 1.7.10 will start issuing a warning about this change,
- to encourage you to tell the command what to push out, e.g. by setting
- push.default configuration.
+ locally have. In future versions of Git, this will change to and push
+ out only your current branch according to either "upstream" or "current"
+ rule (we haven't yet decided which).
Updates since v1.7.9
Junio C Hamano <gitster@pobox.com>