should happen upon such a push by setting the configuration variable
receive.denyDeleteCurrent in the receiving repository.
+In a future release, the default of "git push" without further
+arguments might be changed. Currently, it will push all matching
+refspecs to the current remote. A configuration variable push.default
+has been introduced to select the default behaviour. To ease the
+transition, a big warning is issued if this is not configured and a
+git push without arguments is attempted.
+
Updates since v1.6.2
--------------------
Here are fixes that this release has, but have not been backported to
v1.6.2.X series.
-* "git diff --pickaxe-regexp" did not count overlapping matches
- correctly (backport by cherry-picking 50fd699).
-
-* "git-fetch" in a repository that was not cloned from anywhere said
- it cannot find 'origin', which was hard to understand for new people.
-
* git-gc spent excessive amount of time to decide if an object appears
in a locally existing pack (if needed, backport by merging 69e020a).
-* "git-ls-files --deleted" did not work well with GIT_DIR&GIT_WORK_TREE
- (backport by cherry-picking 8ad3dae).
-
-* "git-read-tree A B C..." without -m option has been broken for a long time
- (backport by merging jc/maint-1.6.0-read-tree-overlay)
-
-* 'git-submodule add' did not tolerate extra slashes and ./ in the
- path it accepted from the command line; it now is more lenient
- (if needed, backport by merging db75ada).
-
-* git-send-email ignored --in-reply-to when --no-thread was given
- (backport by merging tr/maint-1.6.0-send-email-irt)
-
---
exec >/var/tmp/1
O=v1.6.2.1-213-g7d4e3a7