On 1/9/20 4:51 AM, Thomas Huth wrote:
> Python 2 support has been removed, so we should now also remove
> the announcement text for the deprecation.
>
> Signed-off-by: Thomas Huth <th...@redhat.com>
Reviewed-by: John Snow <js...@redhat.com>
> ---
> qemu-deprecated.texi | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/qemu-deprecated.texi b/qemu-deprecated.texi
> index 7033e531de..8b23e98474 100644
> --- a/qemu-deprecated.texi
> +++ b/qemu-deprecated.texi
> @@ -341,14 +341,6 @@ they have no effect when used with @option{-n} to skip
> image creation.
> Silently ignored options can be confusing, so this combination of
> options will be made an error in future versions.
>
> -@section Build system
> -
> -@subsection Python 2 support (since 4.1.0)
> -
> -In the future, QEMU will require Python 3 to be available at
> -build time. Support for Python 2 in scripts shipped with QEMU
> -is deprecated.
> -
> @section Backwards compatibility
>
> @subsection Runnability guarantee of CPU models (since 4.1.0)
>
Genuine question, I'm sorry:
Is it worth documenting things we recently removed? Right now, we don't
really have these docs hosted in a searchable way online in a
per-version format. Once the notice is gone, it's gone from the mirror.
I removed some bitmap functionality not too long ago and I created a
"Recently Removed" section as a bit of a troubleshooting guide should it
be needed.
- Do we want this section?
- Should I remove it?
- Can we add historical docs to the website to see previous deprecated
docs in a searchable manner?
--js
