threads / discuss / 46137

Missing git-2.13.1.* files in the SHA256 sums

Subject: Missing git-2.13.1.* files in the SHA256 sums

## tl;dr

2 messages between Jun 7, 2017 and Jun 12, 2017.

replies: 1people: 2as markdown or json

Andrés Sicard-Ramírez· Jun 7, 2017, 21:00 UTC · lore
Dear all.
The git-2.13.1.* files are missing in
  https://www.kernel.org/pub/software/scm/git/sha256sums.asc
All the best,

-- Andrés La información contenida en este correo electrónico está dirigida únicamente a su destinatario y puede contener información confidencial, material privilegiado o información protegida por derecho de autor. Está prohibida cualquier copia, utilización, indebida retención, modificación, difusión, distribución o reproducción total o parcial. Si usted recibe este mensaje por error, por favor contacte al remitente y elimínelo. La información aquí contenida es responsabilidad exclusiva de su remitente por lo tanto la Universidad EAFIT no se hace responsable de lo que el mensaje contenga. The information contained in this email is addressed to its recipient only and may contain confidential information, privileged material or information protected by copyright. Its prohibited any copy, use, improper retention, modification, dissemination, distribution or total or partial reproduction. If you receive this message by error, please contact the sender and delete it. The information contained herein is the sole responsibility of the sender therefore Universidad EAFIT is not responsible for what the message contains.

Junio C Hamano· Jun 12, 2017, 15:24 UTC · re: Andrés Sicard-Ramírez · lore

Re: Missing git-2.13.1.* files in the SHA256 sums

Andrés Sicard-Ramírez <asr@eafit.edu.co> writes:
Show 5 quoted lines
> The git-2.13.1.* files are missing in
>
>   https://www.kernel.org/pub/software/scm/git/sha256sums.asc
>
> All the best,

These checksum files are auto-generated as part of the mirroring infrastructure among the kernel.org servers, and those who upload to kernel.org (like me) do not have direct control over it. I see that it was a bit lagging when you observed it, but it seems that it has caught up now.

Thanks.

← back to recent threads