From: "Kristian Fiskerstrand (k_f)" <k_f@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-crypt/pinentry/files: pinentry-0.9.1-memleak.patch
Date: Sun, 7 Jun 2015 15:31:46 +0000 (UTC) [thread overview]
Message-ID: <20150607153146.72B7DA2E@oystercatcher.gentoo.org> (raw)
k_f 15/06/07 15:31:46
Removed: pinentry-0.9.1-memleak.patch
Log:
Remove a redundant patch file after previous cleanup
(Portage version: 2.2.18/cvs/Linux x86_64, signed Manifest commit with key 0x250B7AFED6379D85!)
next reply other threads:[~2015-06-07 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 15:31 Kristian Fiskerstrand (k_f) [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-03 15:17 [gentoo-commits] gentoo-x86 commit in app-crypt/pinentry/files: pinentry-0.9.1-memleak.patch Alon Bar-Lev (alonbl)
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=20150607153146.72B7DA2E@oystercatcher.gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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