From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 0/3] glep-0074: clarifications about size and checksum fields
Date: Sun, 25 Sep 2022 21:05:54 +0200 [thread overview]
Message-ID: <af9c4c69d2ab8adce12a1cd5ebc69a03b7845b22.camel@gentoo.org> (raw)
In-Reply-To: <QkvYoVgt73eMzHYSD8Eap3VUzDR0vaEXeNdwJ5v_y31AYGMVAqXVKE_800nr7LbFEpXXGXieEmTf1EyGqx7BblGajbkvioiJ7HbojyRZlu8=@protonmail.com>
On Fri, 2022-09-23 at 17:58 +0000, Sheng Yu wrote:
> Hi,
>
> The hash does not need to be lowercase. It can be a quick fix in portage to accept any case.
>
I'm all for fixing Portage but I don't think we should be breaking
backwards compatibility over this.
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2022-09-25 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:03 [gentoo-dev] [PATCH 0/3] glep-0074: clarifications about size and checksum fields Michał Górny
2022-09-23 14:03 ` [gentoo-dev] [PATCH 1/3] glep-0074: Clarify that DIST entries are specific to PMs Michał Górny
2022-09-23 14:03 ` [gentoo-dev] [PATCH 2/3] glep-0074: Specify the format of size and checksum fields Michał Górny
2022-09-24 23:09 ` John Helmert III
2022-09-25 19:06 ` Michał Górny
2022-09-23 14:03 ` [gentoo-dev] [PATCH 3/3] glep-0074: Clarify the hex encoding of hash values Michał Górny
2022-09-23 17:58 ` [gentoo-dev] [PATCH 0/3] glep-0074: clarifications about size and checksum fields Sheng Yu
2022-09-24 7:34 ` Ulrich Mueller
2022-09-25 19:05 ` Michał Górny [this message]
2022-09-25 19:07 ` [gentoo-dev] [PATCH v2 " Michał Górny
2022-09-25 19:07 ` [gentoo-dev] [PATCH v2 1/3] glep-0074: Clarify that DIST entries are specific to PMs Michał Górny
2022-09-25 19:07 ` [gentoo-dev] [PATCH v2 2/3] glep-0074: Specify the format of size and checksum fields Michał Górny
2022-09-25 19:07 ` [gentoo-dev] [PATCH v2 3/3] glep-0074: Clarify the hex encoding of hash values Michał Górny
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=af9c4c69d2ab8adce12a1cd5ebc69a03b7845b22.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox