public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 2/3] glep-0074: Specify the format of size and checksum fields
Date: Sun, 25 Sep 2022 21:06:32 +0200	[thread overview]
Message-ID: <8722970be35fbb87a04faf470d1d81867efcb7a0.camel@gentoo.org> (raw)
In-Reply-To: <Yy+OHRpD2GF0NFxV@gentoo.org>

On Sat, 2022-09-24 at 18:09 -0500, John Helmert III wrote:
> On Fri, Sep 23, 2022 at 04:03:54PM +0200, Michał Górny wrote:
> > Signed-off-by: Michał Górny <mgorny@gentoo.org>
> > ---
> >  glep-0074.rst | 13 +++++++++++++
> >  1 file changed, 13 insertions(+)
> > 
> > diff --git a/glep-0074.rst b/glep-0074.rst
> > index 54bf216..bfbe092 100644
> > --- a/glep-0074.rst
> > +++ b/glep-0074.rst
> > @@ -191,6 +191,19 @@ The encoding can be used for other characters as well. In particular,
> >  escaping non-printable characters might be desirable.
> >  
> >  
> > +Size and checksum fields
> > +------------------------
> > +
> > +The Manifest entries used to describe files list the file size and one
> > +or more checksums. The size is expressed as an unsigned decimal integer.
> 
> "an unsigned decimal integer" representing the file's size in bytes
> (rather than bits, or nibbles, or $UNIT), right?
> 

Very well.  I'm afraid this is going to break some existing
implementations that preferred to measure in inches but gotta live with
it.

-- 
Best regards,
Michał Górny



  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 [this message]
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
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=8722970be35fbb87a04faf470d1d81867efcb7a0.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