Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable

To: "M. Zhou" <lumin@debian.org>, Cordell Bloor <cgmb@slerp.xyz>, ROCm Team <debian-ai@lists.debian.org>
Subject: Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
From: Christian Kastner <ckk@debian.org>
Date: Sun, 26 Feb 2023 09:04:15 +0100
Message-id: <[🔎] 7582171d-0838-f891-0abe-5d067cf0c487@debian.org>
In-reply-to: <[🔎] 78b4d79b57b3d2fb2238530e51abd3b3ac2efc0f.camel@debian.org>
References: <[🔎] E1pVdIi-007VsO-0p@fasolo.debian.org> <[🔎] 78b4d79b57b3d2fb2238530e51abd3b3ac2efc0f.camel@debian.org>

Hi Mo,

On 2023-02-26 06:25, M. Zhou wrote:
> I suppose this ought to be a source-only upload?

this upload with binaries was in order to pass NEW, a source-only upload
will follow shortly.

Best,
Christian

Reply to:

Follow-Ups:
- Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
  - From: "M. Zhou" <lumin@debian.org>

References:
- hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
  - From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
  - From: "M. Zhou" <lumin@debian.org>

Prev by Date: Re: pytorch and CUDA
Next by Date: Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
Previous by thread: Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
Next by thread: Re: hipcub_5.3.3-1_amd64.changes ACCEPTED into unstable
Index(es):
- Date
- Thread