All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "Rahul.Taya@kpit.com" <Rahul.Taya@kpit.com>,
	"raj.khem@gmail.com" <raj.khem@gmail.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Cc: "nisha.parrakat@kpit.com" <nisha.parrakat@kpit.com>,
	"harpritkaur.bhandari@kpit.com" <harpritkaur.bhandari@kpit.com>
Subject: Re: [oe] [meta-python2][dunfell][PATCH] python: Add fix for CVE-2019-9674
Date: Fri, 19 Feb 2021 02:02:06 +0000	[thread overview]
Message-ID: <35a621b6fbc2297e4ee7508aaaeaae60d67eb441.camel@intel.com> (raw)
In-Reply-To: <20210216152349.30824-1-Rahul.Taya@kpit.com>

On Tue, 2021-02-16 at 20:53 +0530, Rahul Taya wrote:
> +* bpo-36260: Add pitfalls to zipfile module documentation
> +
> +We saw vulnerability warning description (including zip bomb) in
> Doc/library/xml.rst file.
> +This gave us the idea of documentation improvement.
> +
> +So, we moved a little bit forward :P
> +And the doc patch can be found (pr).
> +
> +* fix trailing whitespace
> +
> +* 📜🤖 Added by blurb_it.
> +
> +* Reformat text for consistency.
> +
> +Upstream-Status:
> Backport[
> http://archive.ubuntu.com/ubuntu/pool/main/p/python3.5/python3.5_3.5.2-2ubuntu0~16.04.12.debian.tar.xz
> ]

It looks like this is just a documentation change that is changing a
file that I don't think we package. Is this something that we should
care about?

Thanks,

Anuj


      parent reply	other threads:[~2021-02-19  2:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 15:23 [meta-python2][dunfell][PATCH] python: Add fix for CVE-2019-9674 Rahul Taya
2021-02-18 15:19 ` [oe] " akuster
2021-02-18 17:29   ` Martin Jansa
2021-02-18 17:28 ` Martin Jansa
2021-02-25  8:09   ` Rahul Taya
2021-02-25 14:55     ` Martin Jansa
2021-02-25 16:19       ` Rahul Taya
2021-02-25 17:03         ` Martin Jansa
2021-03-01 14:25           ` Rahul Taya
2021-03-01 14:46             ` Martin Jansa
2021-03-03 13:51               ` Rahul Taya
2021-03-03 14:33                 ` Martin Jansa
     [not found]                   ` <BMXPR01MB3431C751D5DCF36F6DC7B1C1F2989@BMXPR01MB3431.INDPRD01.PROD.OUTLOOK.COM>
2021-03-03 15:52                     ` Martin Jansa
2021-03-16  7:25                       ` Rahul Taya
2021-03-17  4:43                         ` akuster
2021-03-17  7:01                           ` Rahul Taya
     [not found]   ` <8614.1614238566433967267@lists.openembedded.org>
2021-02-25 11:58     ` Private: " Martin Jansa
2021-02-19  2:02 ` Anuj Mittal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35a621b6fbc2297e4ee7508aaaeaae60d67eb441.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=Rahul.Taya@kpit.com \
    --cc=harpritkaur.bhandari@kpit.com \
    --cc=nisha.parrakat@kpit.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.