From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/guilt/
Date: Sat, 19 Aug 2017 00:31:02 +0000 (UTC) [thread overview]
Message-ID: <1503102641.6bfc0d5fbc317beb83cf64fbd40a4bc57a9325a2.whissi@gentoo> (raw)
commit: 6bfc0d5fbc317beb83cf64fbd40a4bc57a9325a2
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 19 00:00:47 2017 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Sat Aug 19 00:30:41 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6bfc0d5f
dev-vcs/guilt: x86 stable (bug #617594)
Package-Manager: Portage-2.3.5, Repoman-2.3.2
dev-vcs/guilt/guilt-0.36.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-vcs/guilt/guilt-0.36.ebuild b/dev-vcs/guilt/guilt-0.36.ebuild
index 10bdef0bae6..af5998c3b1a 100644
--- a/dev-vcs/guilt/guilt-0.36.ebuild
+++ b/dev-vcs/guilt/guilt-0.36.ebuild
@@ -9,7 +9,7 @@ SRC_URI="${HOMEPAGE}/snapshot/22d785dd24329170f66e7696da38b3e90e033d61.tar.gz ->
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 ~ia64 ~ppc ~sparc ~x86"
+KEYWORDS="amd64 ~ia64 ~ppc ~sparc x86"
IUSE=""
# Since we need to build the man pages anyway, I don't think it makes
next reply other threads:[~2017-08-19 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 0:31 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-04 9:23 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/guilt/ Jeroen Roovers
2019-02-20 21:40 Pacho Ramos
2019-02-20 13:16 Mikle Kolyada
2019-02-15 1:37 Thomas Deutschmann
2017-10-07 12:31 Michael Palimaka
2017-10-07 11:26 Sergei Trofimovich
2017-07-19 18:06 Tobias Klausmann
2017-06-02 17:31 David Seifert
2017-05-05 19:31 Michael Orlitzky
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=1503102641.6bfc0d5fbc317beb83cf64fbd40a4bc57a9325a2.whissi@gentoo \
--to=whissi@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