All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helen Mae Koike Fornazier <helen.koike@collabora.com>
To: "WangYuli" <wangyuli@uniontech.com>
Cc: "maarten.lankhorst" <maarten.lankhorst@linux.intel.com>,
	"mripard" <mripard@kernel.org>,
	"tzimmermann" <tzimmermann@suse.de>,
	"airlied" <airlied@gmail.com>, "simona" <simona@ffwll.ch>,
	"david.heidelberg" <david.heidelberg@collabora.com>,
	"dri-devel" <dri-devel@lists.freedesktop.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	"guanwentao" <guanwentao@uniontech.com>,
	"zhanjun" <zhanjun@uniontech.com>,
	"Vignesh Raman" <vignesh.raman@collabora.com>
Subject: Re: [RESEND. PATCH 1/5] drm/ci: Upgrade requirements because of bothering by GitHub Dependabot
Date: Tue, 29 Oct 2024 07:37:33 -0300	[thread overview]
Message-ID: <192d7da2f2a.1069aaa001047791.5583301334791429946@collabora.com> (raw)
In-Reply-To: <11312D359DDCA3CF+20241017034004.113456-1-wangyuli@uniontech.com>





---- On Thu, 17 Oct 2024 00:39:48 -0300 WangYuli  wrote ---

 > GitHub Dependabot keeps bugging us about old, vulnerable Python packages. 
 >  
 > Until we figure out a way to make it calm, we're stuck updating our 
 > dependencies whenever it complains. 
 >  
 > I guess it's a good thing in the long run, though, right? 
 > Makes our CI a bit "more secure"... 
 >  
 > Signed-off-by: WangYuli wangyuli@uniontech.com> 
 > -- 
 > 2.45.2 
 >  
 > 


Hi WangYuli,

Thanks for this.

tbh, I'm tempted in removing the python script that is in the repo, and keep it out-of-tree somewhere, since it is a tool that is only triggered manually in local environment.

I also want to hear Vignesh's thoughts about it.

Thanks
Helen

  reply	other threads:[~2024-10-29 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  3:39 [RESEND. PATCH 1/5] drm/ci: Upgrade requirements because of bothering by GitHub Dependabot WangYuli
2024-10-29 10:37 ` Helen Mae Koike Fornazier [this message]
2024-10-29 10:47   ` Vignesh Raman
2024-10-31  5:42     ` WangYuli

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=192d7da2f2a.1069aaa001047791.5583301334791429946@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=airlied@gmail.com \
    --cc=david.heidelberg@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guanwentao@uniontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=vignesh.raman@collabora.com \
    --cc=wangyuli@uniontech.com \
    --cc=zhanjun@uniontech.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.