qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qemu-web PATCH] pages: update deprecation policy links to "official


From: Thomas Huth
Subject: Re: [qemu-web PATCH] pages: update deprecation policy links to "official" manual
Date: Mon, 8 Mar 2021 12:08:54 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0

On 08/03/2021 11.30, Alex Bennée wrote:
The links are broken now so lets point them at the right place.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
  _posts/2017-08-10-deprecation.md | 2 +-
  download.html                    | 2 +-
  2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/_posts/2017-08-10-deprecation.md b/_posts/2017-08-10-deprecation.md
index d0a7a35..4d007fc 100644
--- a/_posts/2017-08-10-deprecation.md
+++ b/_posts/2017-08-10-deprecation.md
@@ -16,7 +16,7 @@ it.
  Thus we are currently considering to get rid of some of the old interfaces
  and features in a future release and have started to collect a list of such
  old items in our
-[QEMU 
documentation](https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features).
+[QEMU documentation](https://qemu.org/docs/master/system/deprecated.html).
  If you are running QEMU directly, please have a look at this deprecation
  chapter of the QEMU documentation to see whether you are still using one of
  these old interfaces or features, so you can adapt your setup to use the new
diff --git a/download.html b/download.html
index 3c2df66..e3fc789 100644
--- a/download.html
+++ b/download.html
@@ -58,7 +58,7 @@ permalink: /download/
      <strong>do not</strong> have any bearing on the scope of changes
      included in the release. Non-backward compatible changes may be made
      in any master branch release, provided they have followed the
-    <a 
href="https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features";>deprecation 
policy</a>
+    <a href="https://qemu.org/docs/master/system/deprecated.html";>deprecation 
policy</a>
      which calls for warnings to be emitted for a minimum of two releases
      prior to the change.
    </p>


Thanks, pushed.

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]