All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Add elementtree checksum
Date: Mon, 02 Mar 2009 20:16:58 -0500	[thread overview]
Message-ID: <49AC850A.2070702@balister.org> (raw)
In-Reply-To: <1236007399.6800.1133.camel@alap>

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

Angus Ainslie wrote:
> Please advise me if there are policies for applying patches to
> checksums.ini

Normally I do this:

$ mv checksums.ini checksums.ini.old
$ vi checksum.ini.old and add the new entry at the top of the file
$ python ../contrib/source-checker/oe-checksums-sorter.py 
checksums.ini.old > checksums.ini

Then remove the .old file, run a quick test and commit.

Philip

> 
> 
> Thanks
> Angus
> 
> ---
>  conf/checksums.ini |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/conf/checksums.ini b/conf/checksums.ini
> index 52e26d6..497dd07 100644
> --- a/conf/checksums.ini
> +++ b/conf/checksums.ini
> @@ -1,3 +1,7 @@
> +[http://effbot.org/media/downloads/elementtree-1.2.7-20070827-preview.zip]
> +md5=30e2fe5edd143f347e03a8baf5d60f8a
> +sha256=5071431068c58c1f56dcc8fff37f8a213351f3b45c012d3adb640ec9418053ad
> +
>  [http://www.directfb.org/downloads/Extras/++DFB-0.9.25.tar.gz]
>  md5=c6a2705f6210d8ede50a947b375f1c0b
>  sha256=b3dbf01563dd60d63cff543ea8cd0c885381e78ecbbab8ff176e46df3f198a88
> --
> 1.5.6.3
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

      reply	other threads:[~2009-03-03  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 15:23 [PATCH] Add elementtree checksum Angus Ainslie
2009-03-03  1:16 ` Philip Balister [this message]

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=49AC850A.2070702@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.