All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] ofono: bump to version 1.16
Date: Mon, 16 Mar 2015 09:36:22 +0100	[thread overview]
Message-ID: <87pp89e3uh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1426493904-16521-2-git-send-email-petr.vorel@gmail.com> (Petr Vorel's message of "Mon, 16 Mar 2015 09:18:24 +0100")

>>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes:

 > Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
 > ---
 >  package/ofono/ofono.hash | 1 +
 >  package/ofono/ofono.mk   | 2 +-
 >  2 files changed, 2 insertions(+), 1 deletion(-)
 >  create mode 100644 package/ofono/ofono.hash

 > diff --git a/package/ofono/ofono.hash b/package/ofono/ofono.hash
 > new file mode 100644
 > index 0000000..e607ba5
 > --- /dev/null
 > +++ b/package/ofono/ofono.hash
 > @@ -0,0 +1 @@
 > +sha256	403b98dadece8bc804c0bd16b96d3db5a3bb0f84af64b3d67924da2d1a754b07  ofono-1.16.tar.xz

You are missing a comment about where this hash comes from. Upstream
provides gpg signagtures, so I've verified that and added a comment
about it.

Committed with that fixed, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2015-03-16  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  8:18 [Buildroot] [PATCH 1/2] connman: bump to version 1.28 Petr Vorel
2015-03-16  8:18 ` [Buildroot] [PATCH 2/2] ofono: bump to version 1.16 Petr Vorel
2015-03-16  8:24   ` Baruch Siach
2015-03-16  8:36   ` Peter Korsgaard [this message]
2015-03-16  8:35 ` [Buildroot] [PATCH 1/2] connman: bump to version 1.28 Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2015-03-16  8:28 [Buildroot] [PATCH 2/2] ofono: bump to version 1.16 Petr Vorel
2015-03-16  8:40 ` Peter Korsgaard
2015-03-16  7:33 [Buildroot] [PATCH 1/2] connman: bump to version 1.28 Petr Vorel
2015-03-16  7:33 ` [Buildroot] [PATCH 2/2] ofono: bump to version 1.16 Petr Vorel

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=87pp89e3uh.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 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.