From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 0/6] glep-0078: Clarifications
Date: Wed, 21 Sep 2022 20:16:45 +0200 [thread overview]
Message-ID: <20220921181651.39370-1-mgorny@gentoo.org> (raw)
Hi,
Here's a bunch of patches to GLEP 78 (GPKG format). They're mostly
clarifications, that is:
- replacing "basename" with more specific explanation
- linking formats to the respective standards
- deferring compressed file formats to GLEP 74
- clarifying the situation around Manifest signing and verifying binpkg
authenticity
Please review.
Michał Górny (6):
glep-0078: Replace "basename" with non-ambiguous explanation
glep-0078: Link tar format to the respective standards
glep-0078: Link compressed file formats to GLEP 74
glep-0078: Link OpenPGP to RFC 4880
glep-0078: Clarify that Manifest is signed too
glep-0078: Clarify that Manifest must be present for signed binpkg
glep-0078.rst | 64 +++++++++++++++++++++++++++++++++++----------------
1 file changed, 44 insertions(+), 20 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-21 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 18:16 Michał Górny [this message]
2022-09-21 18:16 ` [gentoo-dev] [PATCH 1/6] glep-0078: Replace "basename" with non-ambiguous explanation Michał Górny
2022-09-22 6:07 ` Ulrich Mueller
2022-09-21 18:16 ` [gentoo-dev] [PATCH 2/6] glep-0078: Link tar format to the respective standards Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 3/6] glep-0078: Link compressed file formats to GLEP 74 Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 4/6] glep-0078: Link OpenPGP to RFC 4880 Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 5/6] glep-0078: Clarify that Manifest is signed too Michał Górny
2022-09-21 18:16 ` [gentoo-dev] [PATCH 6/6] glep-0078: Clarify that Manifest must be present for signed binpkg 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=20220921181651.39370-1-mgorny@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