Hi Dmitry,
On 29/04/25 23:51, Dmitry Baryshkov wrote:
On Thu, Apr 03, 2025 at 11:29:55AM +0530, Vignesh Raman wrote:
Hi Daniel,
On 28/03/25 17:29, Vignesh Raman wrote:
Hi Daniel,
On 28/03/25 17:06, Daniel Stone wrote:
Hi Vignesh,
On Fri, 28 Mar 2025 at 11:03, Vignesh Raman
wrote:
The cur
On Thu, Apr 03, 2025 at 11:29:55AM +0530, Vignesh Raman wrote:
> Hi Daniel,
>
> On 28/03/25 17:29, Vignesh Raman wrote:
> > Hi Daniel,
> >
> > On 28/03/25 17:06, Daniel Stone wrote:
> > > Hi Vignesh,
> > >
> > > On Fri, 28 Mar 2025 at 11:03, Vignesh Raman
> > > wrote:
> > > > The current s3cp i
Hi Daniel,
On 28/03/25 17:06, Daniel Stone wrote:
Hi Vignesh,
On Fri, 28 Mar 2025 at 11:03, Vignesh Raman wrote:
The current s3cp implementation does not work anymore after the
migration, and instead of fixing it and propagating the fix down to us,
it's simpler to directly use curl. Uprev mes
Hi Daniel,
On 28/03/25 17:29, Vignesh Raman wrote:
Hi Daniel,
On 28/03/25 17:06, Daniel Stone wrote:
Hi Vignesh,
On Fri, 28 Mar 2025 at 11:03, Vignesh Raman
wrote:
The current s3cp implementation does not work anymore after the
migration, and instead of fixing it and propagating the fix do
Hi Vignesh,
On Fri, 28 Mar 2025 at 11:03, Vignesh Raman wrote:
> The current s3cp implementation does not work anymore after the
> migration, and instead of fixing it and propagating the fix down to us,
> it's simpler to directly use curl. Uprev mesa [1][2] to adapt these
> changes. Also replace
The current s3cp implementation does not work anymore after the
migration, and instead of fixing it and propagating the fix down to us,
it's simpler to directly use curl. Uprev mesa [1][2] to adapt these
changes. Also replace broken s3cp command with a curl wrapper call in
drm-ci.
[1] https://gitl
