From: Dirk Opfer <Dirk@Do13.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libcap, libcap2: use automatic packaging to fix QA errors
Date: Mon, 10 Jan 2011 22:15:47 +0100 [thread overview]
Message-ID: <4D2B7703.2030605@Do13.de> (raw)
In-Reply-To: <1294670726.4342.72.camel@mattotaupa>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
Am 10.01.2011 15:45, schrieb Paul Menzel:
> Maybe you want to look deeper into the history of that file. Sorry.
> It looks Dirk committed these lines when adding 1.10 in commit b823b4
> [1].
>
> Dirk, could you please comment on [2].
>
No idea why this was needed in the old version.
Looks fine to me.
Acked-by: Dirk Opfer <dirk@do13.de>
Thanks,
Dirk
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3530 bytes --]
prev parent reply other threads:[~2011-01-10 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 14:56 libcap_1.10: ERROR: QA Issue with libcap: non -dev package contains symlink .so Paul Menzel
2011-01-09 18:20 ` Khem Raj
2011-01-10 11:39 ` [PATCH] libcap, libcap2: use automatic packaging to fix QA errors Paul Menzel
2011-01-10 13:44 ` Rolf Leggewie
2011-01-10 14:45 ` Paul Menzel
2011-01-10 21:11 ` Dirk Opfer
2011-01-10 21:15 ` Dirk Opfer [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=4D2B7703.2030605@Do13.de \
--to=dirk@do13.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox