Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes
Date: Thu, 6 Mar 2014 18:37:03 +0100	[thread overview]
Message-ID: <20140306173703.GD3625@free.fr> (raw)
In-Reply-To: <CAAXf6LUexBaQVBvqZ5J5k895fqkv5qoX01pVeCuoEOpyO8O8Lg@mail.gmail.com>

Thomas, All,

On 2014-03-06 18:14 +0100, Thomas De Schampheleire spake thusly:
> On Wed, Mar 5, 2014 at 10:47 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
> > index e56e59a..4609a7e 100644
> > --- a/docs/manual/adding-packages-directory.txt
> > +++ b/docs/manual/adding-packages-directory.txt
[--SNIP--]
> > +* the name of the file, without any directory component
> > +
> > +Lines starting with a +#+ sign are considered comments, and ignored. Empty
> > +lines are ignored.
> > +
> > +There can be more than one hash for a single file, each of its own line. In
> 
> I think you can say:
> ..., each on its own line
> ..., each on a line of its own
> but not 'each of its own line'

Funny how one reads what one thinks he has written, and not what was
actually written. Of course, I meant 'on', not 'of'.

> > +this case, all hashes must match.
> > +
> > +Ideally, the hashes stored in this file should match the hashes published by
> > +upstream, eg, on their website, in the email announcement... If no such info
> 
> 'eg' should be written with dots (e.g. , see
> http://en.wikipedia.org/wiki/Exempli_gratia#exempli_gratia )
> e-mail (with dash)
> 
> > +is available, then compute them yourself, and state so in a comment line
> > +above the hashes.
> 
> I would write for this last sentence:
> If upstream does not provide hashes, [...]

Furthermore, since there is no hash, it can be plural. I now wrote:

    If upstream does not provide any hash, [...]

All applied. Thank you!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-03-06 17:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 21:47 [Buildroot] [PATCH 0/12 v3] some download-related changes Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 01/12] Makefile: rename USER_HOOKS_EXTRA_ENV to EXTRA_ENV Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 02/12] Makefile: add BR2_DL_DIR " Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 03/12] pkg-infra: move the git download helper to a script Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 04/12] pkg-infra: move the svn " Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 05/12] pkg-infra: move the cvs " Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 06/12] pkg-infra: move the hg " Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 07/12] pkg-infra: move the wget " Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 08/12] pkg-infra: don't use DL_DIR as scratchpad for temporary VCS checkouts Yann E. MORIN
2014-03-06 10:25   ` Samuel Martin
2014-03-06 16:54     ` Yann E. MORIN
2014-03-06 17:45     ` Arnout Vandecappelle
2014-03-05 21:47 ` [Buildroot] [PATCH 09/12] pkg-infra: also set PKGDIR for the download step Yann E. MORIN
2014-03-05 21:47 ` [Buildroot] [PATCH 10/12] pkg-infra: add possiblity to check downloaded files against known hashes Yann E. MORIN
2014-03-06 10:45   ` Samuel Martin
2014-03-05 21:47 ` [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes Yann E. MORIN
2014-03-06 10:56   ` Samuel Martin
2014-03-06 17:09     ` Yann E. MORIN
2014-03-06 17:14   ` Thomas De Schampheleire
2014-03-06 17:37     ` Yann E. MORIN [this message]
2014-03-05 21:47 ` [Buildroot] [PATCH 12/12] package/ca-certificates: add tarball's hashes Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2014-03-10 20:51 [Buildroot] [PATCH 0/12 v4] Some download-related changes (branch yem/check-downloads) Yann E. MORIN
2014-03-10 20:51 ` [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes Yann E. MORIN
2014-03-11 10:37   ` Thomas De Schampheleire
2014-06-01 17:40 [Buildroot] [PATCH 0/12 v6] Some download-related changes (branch yem/check-downloads) Yann E. MORIN
2014-06-01 17:40 ` [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes Yann E. MORIN
2014-06-01 20:08   ` Samuel Martin
2014-06-01 20:13     ` Yann E. MORIN
2014-06-08 20:43 [Buildroot] [PATCH 0/12 v7] Some download-related changes (branch yem/check-downloads) Yann E. MORIN
2014-06-08 20:43 ` [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes Yann E. MORIN
2014-07-02 21:11 [Buildroot] [PATCH 0/12 v10] Some download-related changes (branch yem/check-downloads) Yann E. MORIN
2014-07-02 21:11 ` [Buildroot] [PATCH 11/12] manual: add documentation about packages' hashes Yann E. MORIN

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=20140306173703.GD3625@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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