From: "Agostino Sarubbo (ago)" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-libs/libseccomp: libseccomp-1.0.1.ebuild ChangeLog
Date: Mon, 14 Jan 2013 19:01:20 +0000 (UTC) [thread overview]
Message-ID: <20130114190120.AF18C2171D@flycatcher.gentoo.org> (raw)
ago 13/01/14 19:01:20
Modified: libseccomp-1.0.1.ebuild ChangeLog
Log:
Stable for amd64, wrt bug #451496
(Portage version: 2.1.11.31/cvs/Linux x86_64, unsigned Manifest commit)
Revision Changes Path
1.2 sys-libs/libseccomp/libseccomp-1.0.1.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild?r1=1.1&r2=1.2
Index: libseccomp-1.0.1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- libseccomp-1.0.1.ebuild 6 Jan 2013 23:07:45 -0000 1.1
+++ libseccomp-1.0.1.ebuild 14 Jan 2013 19:01:20 -0000 1.2
@@ -1,6 +1,6 @@
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild,v 1.1 2013/01/06 23:07:45 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/libseccomp-1.0.1.ebuild,v 1.2 2013/01/14 19:01:20 ago Exp $
# Note: USE=static-libs isn't great -- only PIC objects are provided.
@@ -14,7 +14,7 @@
LICENSE="LGPL-2"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE="static-libs tools"
src_prepare() {
1.6 sys-libs/libseccomp/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/ChangeLog?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/ChangeLog?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-libs/libseccomp/ChangeLog?r1=1.5&r2=1.6
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/ChangeLog,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ChangeLog 6 Jan 2013 23:07:45 -0000 1.5
+++ ChangeLog 14 Jan 2013 19:01:20 -0000 1.6
@@ -1,6 +1,9 @@
# ChangeLog for sys-libs/libseccomp
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/ChangeLog,v 1.5 2013/01/06 23:07:45 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/sys-libs/libseccomp/ChangeLog,v 1.6 2013/01/14 19:01:20 ago Exp $
+
+ 14 Jan 2013; Agostino Sarubbo <ago@gentoo.org> libseccomp-1.0.1.ebuild:
+ Stable for amd64, wrt bug #451496
*libseccomp-1.0.1 (06 Jan 2013)
next reply other threads:[~2013-01-14 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 19:01 Agostino Sarubbo (ago) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 17:26 [gentoo-commits] gentoo-x86 commit in sys-libs/libseccomp: libseccomp-1.0.1.ebuild ChangeLog Agostino Sarubbo (ago)
2013-01-06 23:07 Mike Frysinger (vapier)
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=20130114190120.AF18C2171D@flycatcher.gentoo.org \
--to=ago@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