From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/elogv/
Date: Tue, 19 Nov 2019 07:38:40 +0000 (UTC) [thread overview]
Message-ID: <1574149088.66e83a167fac368d207e7d32e7bd9dcecd1b418b.ago@gentoo> (raw)
commit: 66e83a167fac368d207e7d32e7bd9dcecd1b418b
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 19 07:38:08 2019 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue Nov 19 07:38:08 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=66e83a16
app-portage/elogv: amd64 stable wrt bug #698836
Package-Manager: Portage-2.3.76, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
app-portage/elogv/elogv-0.7.8-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/elogv/elogv-0.7.8-r1.ebuild b/app-portage/elogv/elogv-0.7.8-r1.ebuild
index e5004bc33c8..6d61dd70ff3 100644
--- a/app-portage/elogv/elogv-0.7.8-r1.ebuild
+++ b/app-portage/elogv/elogv-0.7.8-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/gentoo/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="~alpha amd64 ~arm ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
DOCS=( README )
next reply other threads:[~2019-11-19 7:38 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 7:38 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-08 23:13 [gentoo-commits] repo/gentoo:master commit in: app-portage/elogv/ Sebastian Pipping
2023-11-08 12:48 Sebastian Pipping
2023-11-08 8:08 Arthur Zamarin
2023-11-07 17:09 Sam James
2023-11-07 17:09 Sam James
2023-11-07 17:09 Sam James
2023-10-12 9:47 Sam James
2023-10-06 22:14 Sebastian Pipping
2023-10-06 18:04 Sebastian Pipping
2023-10-05 18:42 Sebastian Pipping
2023-10-05 15:07 Sebastian Pipping
2023-10-05 15:07 Sebastian Pipping
2023-09-28 6:17 Sam James
2023-09-28 0:21 Sam James
2023-09-27 5:47 Sam James
2023-07-08 14:30 Sebastian Pipping
2023-04-20 5:01 Sam James
2023-04-20 4:38 Arthur Zamarin
2023-04-20 4:17 Sam James
2023-04-20 4:14 Arthur Zamarin
2022-11-28 20:37 Sebastian Pipping
2022-09-17 13:36 Sebastian Pipping
2022-05-22 16:17 Zac Medico
2022-04-30 18:08 Sebastian Pipping
2021-10-30 22:31 Georgy Yakovlev
2021-02-18 17:12 Sam James
2021-02-17 20:54 Sam James
2021-02-17 15:55 Sergei Trofimovich
2021-02-16 19:22 Sam James
2021-01-06 13:23 Fabian Groffen
2020-11-23 10:22 Sebastian Pipping
2020-10-07 9:55 Georgy Yakovlev
2020-08-21 22:05 Georgy Yakovlev
2020-07-06 0:32 Sebastian Pipping
2020-04-20 9:48 Agostino Sarubbo
2020-04-19 23:55 Sergei Trofimovich
2020-04-19 18:23 Agostino Sarubbo
2020-04-19 17:08 Agostino Sarubbo
2020-03-05 14:46 Sebastian Pipping
2019-11-30 18:59 Sebastian Pipping
2019-11-30 18:59 Sebastian Pipping
2019-11-19 19:45 Sergei Trofimovich
2019-11-19 12:48 Agostino Sarubbo
2019-10-13 20:29 Zac Medico
2019-10-13 20:29 Zac Medico
2018-07-08 16:36 Sebastian Pipping
2018-05-18 17:44 Sebastian Pipping
2018-05-16 18:38 Sebastian Pipping
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=1574149088.66e83a167fac368d207e7d32e7bd9dcecd1b418b.ago@gentoo \
--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