summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAxel Beckert <abe@deuxchevaux.org>2020-02-14 02:48:48 +0100
committerAxel Beckert <abe@deuxchevaux.org>2020-02-14 02:57:12 +0100
commit25d6db7b71f790db9f391334a238012bb6ba2d82 (patch)
tree968e2ea568a4c6696b7a6a6e95d2ed335c1c7a39
parent1515cb64dfa93c9cd8060be6a6cdadb2ba81a55e (diff)
downloadzsh-25d6db7b71f790db9f391334a238012bb6ba2d82.tar.gz
zsh-25d6db7b71f790db9f391334a238012bb6ba2d82.zip
Add NEWS based on incompatibilities listed in upstream's README.
Gbp-Dch: Ignore
-rw-r--r--debian/NEWS29
1 files changed, 29 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS
index 448f88c4f..3b4d0a333 100644
--- a/debian/NEWS
+++ b/debian/NEWS
@@ -1,3 +1,32 @@
+zsh (5.7.1-test-3-1) experimental; urgency=low
+
+ From the upstream README of 5.7.1-test-3:
+
+ > The history expansion !:1:t2 used to be interpreted such that the 2
+ > was a separate character added after the history expansion. Now it is
+ > an argument to the :t modifier.
+ >
+ > For example
+ >
+ > % echo /my/interesting/path
+ > % echo !:1:t2
+ >
+ > used to echo "path2", but now echoes "interesting/path".
+ >
+ > The behaviour of :h has similarly changed.
+ >
+ > The behaviour has also changed in forms such as ${foo:t2) and *(:t2),
+ > but in those cases the previous behaviour was not meaningful.
+ >
+ > The vcs_info function VCS_INFO_quilt-dirfind now returns a string value
+ > by setting $REPLY. Previously it printed the value to standard output.
+ > This only affects you if you override that function in your dotfiles.
+ >
+ > The cd and chdir builtins no longer interpret operands like -1 and +2 as
+ > stack entries when POSIX_CD is enabled.
+
+ -- Axel Beckert <abe@debian.org> Fri, 14 Feb 2020 02:44:59 +0100
+
zsh (5.4.2-1) unstable; urgency=medium
From the upstream README of 5.4.1: