From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] opkg: Add gnupg signature checking support.
Date: Tue, 09 Apr 2013 18:03:45 +0200 [thread overview]
Message-ID: <51643BE1.3000701@mind.be> (raw)
In-Reply-To: <52530026.WMUqvmoQpY@arawn>
On 08/04/13 12:26, Philipp Claves wrote:
> Any status update on merging this patchset?
Thomas sent comments about your patches and we assumed you would that
re-send them taking into account the review feedback. If you are not
planning to send updated patches, please tell us. Then somebody else may
pick up the patches (but don't count on it).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-04-09 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 14:04 [Buildroot] [PATCH] opkg: Add option to enable package verification support with GnuPG Philipp Claves
2013-02-28 14:38 ` Thomas Petazzoni
[not found] ` <2380880.Y2Uig4QfWB@arawn>
2013-03-01 10:18 ` Thomas Petazzoni
2013-03-01 13:38 ` [Buildroot] [PATCH 1/3] Add libassuan IPC library Philipp Claves
2013-03-01 13:38 ` [Buildroot] [PATCH 2/3] Add GnuPG Made Easy (gpgme) library Philipp Claves
2013-03-01 13:38 ` [Buildroot] [PATCH 3/3] opkg: Add gnupg signature checking support Philipp Claves
2013-04-08 10:26 ` Philipp Claves
2013-04-09 16:03 ` Arnout Vandecappelle [this message]
2013-04-10 17:40 ` Thomas Petazzoni
2013-04-26 11:41 ` Philipp Claves
2013-07-31 16:14 ` [Buildroot] [PATCH 1/3] Add libassuan IPC library Thomas Petazzoni
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=51643BE1.3000701@mind.be \
--to=arnout@mind.be \
--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