public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/libudev/
Date: Mon,  2 Dec 2019 11:04:31 +0000 (UTC)	[thread overview]
Message-ID: <1575284643.e193e3add7a1a0415ef435854cf0a04bea6c9d2c.zlogene@gentoo> (raw)

commit:     e193e3add7a1a0415ef435854cf0a04bea6c9d2c
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Mon Dec  2 11:04:03 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Mon Dec  2 11:04:03 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e193e3ad

virtual/libudev: m68k stable wrt bug #698698

Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="m68k"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 virtual/libudev/libudev-232-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/libudev/libudev-232-r2.ebuild b/virtual/libudev/libudev-232-r2.ebuild
index 4423f728471..544c55b027b 100644
--- a/virtual/libudev/libudev-232-r2.ebuild
+++ b/virtual/libudev/libudev-232-r2.ebuild
@@ -6,7 +6,7 @@ inherit multilib-build
 
 DESCRIPTION="Virtual for libudev providers"
 SLOT="0/1"
-KEYWORDS="~alpha amd64 arm arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~riscv s390 sh sparc x86"
+KEYWORDS="~alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 ~riscv s390 sh sparc x86"
 IUSE="static-libs systemd"
 
 RDEPEND="


             reply	other threads:[~2019-12-02 11:04 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 11:04 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-12 14:27 [gentoo-commits] repo/gentoo:master commit in: virtual/libudev/ Mike Gilbert
2023-10-12 14:27 Mike Gilbert
2023-10-12 14:27 Mike Gilbert
2023-09-01 16:07 Arthur Zamarin
2023-08-29 18:02 Arthur Zamarin
2023-08-29 17:55 Arthur Zamarin
2023-08-29 17:49 Arthur Zamarin
2023-07-31 15:22 Mike Gilbert
2023-07-21 12:43 Sam James
2023-07-20 19:12 Matt Turner
2023-06-15  2:03 Sam James
2023-06-15  2:03 Sam James
2022-06-04  2:21 Sam James
2022-06-03  7:05 Sam James
2022-06-03  0:52 Sam James
2022-06-03  0:52 Sam James
2022-06-03  0:37 Sam James
2022-06-02  1:52 Sam James
2022-06-02  1:52 Sam James
2022-05-30  7:15 Sam James
2022-04-17 12:48 Sam James
2022-04-16 23:13 Mike Gilbert
2021-09-07 17:37 Mike Gilbert
2021-08-13 16:18 Mike Gilbert
2021-08-13 16:18 Mike Gilbert
2021-08-09 15:15 Mike Gilbert
2021-07-22 22:45 William Hubbs
2019-12-10  8:47 Agostino Sarubbo
2019-12-03  8:37 Agostino Sarubbo
2019-12-02 11:04 Mikle Kolyada
2019-12-02 11:04 Mikle Kolyada
2019-11-30 21:45 Sergei Trofimovich
2019-11-21 22:20 Matt Turner
2019-11-11 18:09 Aaron Bauman
2019-11-08  3:23 Aaron Bauman
2019-11-04 20:06 Sergei Trofimovich
2019-11-04 20:06 Sergei Trofimovich
2019-11-02  0:42 Matt Turner
2019-11-02  0:42 Matt Turner
2019-11-01 20:09 Matt Turner
2019-11-01 20:09 Matt Turner
2019-11-01 19:30 Mike Gilbert
2019-11-01 10:51 Mikle Kolyada
2019-11-01 10:34 Mikle Kolyada
2019-10-31 23:50 Thomas Deutschmann
2019-10-28 17:12 Mike Gilbert
2019-10-28 17:10 Mike Gilbert
2019-10-28 12:07 Anthony G. Basile
2019-10-27 15:31 Michał Górny
2019-10-27 15:31 Michał Górny
2019-10-27 15:31 Michał Górny
2019-05-04 19:58 Andreas K. Hüttel
2018-04-18  5:54 Mart Raudsepp
2017-09-14 20:19 Sergei Trofimovich
2017-07-13  1:56 Markus Meier
2017-07-12  9:38 Sergei Trofimovich
2017-07-04 18:06 Mike Gilbert
2017-07-04 17:27 Mike Gilbert
2016-11-26 19:41 Mike Gilbert
2016-11-26 19:41 Mike Gilbert
2016-11-04 23:15 William Hubbs

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=1575284643.e193e3add7a1a0415ef435854cf0a04bea6c9d2c.zlogene@gentoo \
    --to=zlogene@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