From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sec-policy/selinux-varnishd: ChangeLog selinux-varnishd-2.20120725-r11.ebuild
Date: Sat, 26 Jan 2013 18:20:36 +0000 (UTC) [thread overview]
Message-ID: <20130126182036.DA0D321720@flycatcher.gentoo.org> (raw)
swift 13/01/26 18:20:36
Modified: ChangeLog
Added: selinux-varnishd-2.20120725-r11.ebuild
Log:
Pushing out rev 11
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0xCDBA2FDB)
Revision Changes Path
1.23 sec-policy/selinux-varnishd/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog?rev=1.23&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog?r1=1.22&r2=1.23
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- ChangeLog 13 Jan 2013 16:03:46 -0000 1.22
+++ ChangeLog 26 Jan 2013 18:20:36 -0000 1.23
@@ -1,6 +1,12 @@
# ChangeLog for sec-policy/selinux-varnishd
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog,v 1.22 2013/01/13 16:03:46 swift Exp $
+# $Header: /var/cvsroot/gentoo-x86/sec-policy/selinux-varnishd/ChangeLog,v 1.23 2013/01/26 18:20:36 swift Exp $
+
+*selinux-varnishd-2.20120725-r11 (26 Jan 2013)
+
+ 26 Jan 2013; Sven Vermeulen <swift@gentoo.org>
+ +selinux-varnishd-2.20120725-r11.ebuild:
+ Bumping selinux-varnishd to revision 11
13 Jan 2013; Sven Vermeulen <swift@gentoo.org>
selinux-varnishd-2.20120725-r9.ebuild:
1.1 sec-policy/selinux-varnishd/selinux-varnishd-2.20120725-r11.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sec-policy/selinux-varnishd/selinux-varnishd-2.20120725-r11.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sec-policy/selinux-varnishd/selinux-varnishd-2.20120725-r11.ebuild?rev=1.1&content-type=text/plain
Index: selinux-varnishd-2.20120725-r11.ebuild
===================================================================
# Copyright 1999-2013 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sec-policy/selinux-varnishd/selinux-varnishd-2.20120725-r11.ebuild,v 1.1 2013/01/26 18:20:36 swift Exp $
EAPI="4"
IUSE=""
MODS="varnishd"
BASEPOL="2.20120725-r9"
inherit selinux-policy-2
DESCRIPTION="SELinux policy for varnishd"
KEYWORDS="~amd64 ~x86"
next reply other threads:[~2013-01-26 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 18:20 Sven Vermeulen (swift) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-23 17:24 [gentoo-commits] gentoo-x86 commit in sec-policy/selinux-varnishd: ChangeLog selinux-varnishd-2.20120725-r11.ebuild Sven Vermeulen (swift)
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=20130126182036.DA0D321720@flycatcher.gentoo.org \
--to=swift@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