public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/time/
Date: Fri, 20 Apr 2018 18:39:36 +0000 (UTC)	[thread overview]
Message-ID: <1524249558.49e6dfd64269320a9e87b1edcde777a27e0fb882.leio@gentoo> (raw)

commit:     49e6dfd64269320a9e87b1edcde777a27e0fb882
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 20 18:35:27 2018 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Fri Apr 20 18:39:18 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=49e6dfd6

sys-process/time-1.7.2: arm64 stable (bug #643016)

Package-Manager: Portage-2.3.28, Repoman-2.3.9

 sys-process/time/time-1.7.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-process/time/time-1.7.2.ebuild b/sys-process/time/time-1.7.2.ebuild
index 733ccd42961..8722f37d269 100644
--- a/sys-process/time/time-1.7.2.ebuild
+++ b/sys-process/time/time-1.7.2.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://git.savannah.gnu.org/cgit/time.git/snapshot/${P}.tar.gz"
 
 LICENSE="GPL-3+"
 SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="alpha amd64 arm arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-linux ~x86-linux"
 IUSE=""
 
 DEPEND="sys-apps/texinfo"


             reply	other threads:[~2018-04-20 18:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 18:39 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-17  1:56 [gentoo-commits] repo/gentoo:master commit in: sys-process/time/ Sam James
2022-12-26  8:35 Sam James
2022-11-04  8:16 Agostino Sarubbo
2022-11-03 19:13 Sam James
2022-11-03 17:24 Arthur Zamarin
2022-11-03 17:24 Arthur Zamarin
2022-11-03 17:24 Arthur Zamarin
2022-11-03 17:24 Arthur Zamarin
2022-11-03 17:24 Arthur Zamarin
2022-11-03 17:24 Arthur Zamarin
2022-10-18  2:18 Sam James
2022-05-19 10:35 WANG Xuerui
2021-12-26 23:38 Sam James
2021-12-26 23:38 Sam James
2021-12-26 19:37 Sam James
2021-12-26 19:31 Sam James
2021-04-16 10:25 David Seifert
2020-09-07  0:59 Sam James
2020-08-29 23:50 Sam James
2020-08-15  7:31 Sergei Trofimovich
2020-08-15  7:26 Sergei Trofimovich
2020-08-15  4:46 Sam James
2020-08-14  6:00 Sam James
2020-08-14  5:10 Sam James
2020-03-21 19:30 Mikle Kolyada
2018-03-23  4:48 Markus Meier
2018-03-23  0:02 Sergei Trofimovich
2018-03-13 15:34 Lars Wendler
2018-03-11  6:08 Matt Turner
2018-03-03 13:12 Tobias Klausmann
2018-02-25 17:34 Mart Raudsepp
2018-01-22  8:15 Sergei Trofimovich
2018-01-21 16:46 Sergei Trofimovich
2018-01-17  5:11 Thomas Deutschmann
2018-01-15 22:06 Sergei Trofimovich
2017-10-06 10:33 Sergei Trofimovich
2017-10-06 10:30 Sergei Trofimovich
2017-10-05 13:15 Sergei Trofimovich
2017-08-25 22:34 Matt Turner
2017-08-14 13:36 Lars Wendler
2017-08-14 13:36 Lars Wendler
2017-08-10  4:40 Markus Meier
2017-08-08 13:06 Manuel Rüger
2017-08-08 13:06 Manuel Rüger
2017-08-05 18:07 Sergei Trofimovich
2017-02-22 18:11 Manuel Rüger
2017-01-29 20:14 Fabian Groffen

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=1524249558.49e6dfd64269320a9e87b1edcde777a27e0fb882.leio@gentoo \
    --to=leio@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