public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/asdf/
Date: Thu, 27 Jan 2022 19:07:33 +0000 (UTC)	[thread overview]
Message-ID: <1643310397.1d2fc5b17044e43102a943874e230f67d0a4bb23.sam@gentoo> (raw)

commit:     1d2fc5b17044e43102a943874e230f67d0a4bb23
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 27 19:06:37 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 27 19:06:37 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d2fc5b1

dev-lisp/asdf: Stabilize 3.3.5 x86, #828735

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-lisp/asdf/asdf-3.3.5.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-lisp/asdf/asdf-3.3.5.ebuild b/dev-lisp/asdf/asdf-3.3.5.ebuild
index 3eea944b4e25..d7c0387571b6 100644
--- a/dev-lisp/asdf/asdf-3.3.5.ebuild
+++ b/dev-lisp/asdf/asdf-3.3.5.ebuild
@@ -11,7 +11,7 @@ SRC_URI="http://common-lisp.net/project/${PN}/archives/${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0/${PVR}"
-KEYWORDS="~alpha ~amd64 ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-solaris"
+KEYWORDS="~alpha ~amd64 ~ia64 ~ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~x64-macos ~x86-solaris"
 IUSE="doc test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2022-01-27 19:07 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 19:07 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-27  7:37 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/asdf/ Ulrich Müller
2023-07-27  6:01 Sam James
2022-05-14 21:52 Jakov Smolić
2022-04-28 15:05 Jakov Smolić
2022-03-04 23:58 Sam James
2022-02-28  5:03 Sam James
2022-02-17 11:13 Jakov Smolić
2022-02-17 11:00 Jakov Smolić
2022-01-31 18:50 Sam James
2022-01-12 20:12 Arthur Zamarin
2022-01-03  1:19 Sam James
2022-01-03  1:19 Sam James
2021-01-06 19:34 Fabian Groffen
2019-11-18 16:25 Ulrich Müller
2018-08-04 12:59 Patrick Lauer
2018-08-04 11:37 Patrick Lauer
2018-05-05 15:39 José María Alonso
2018-05-05 13:42 José María Alonso
2018-03-09 15:03 José María Alonso
2018-03-08 15:21 José María Alonso
2018-03-08 15:21 José María Alonso
2018-03-04 22:12 José María Alonso
2018-03-04 15:56 José María Alonso
2018-03-03 20:27 Andreas Hüttel
2018-03-03 17:56 Sergei Trofimovich
2018-02-19 20:15 Sergei Trofimovich
2018-01-28 16:59 Tobias Klausmann
2017-11-15 18:31 José María Alonso
2017-10-30 19:40 José María Alonso
2017-10-30 15:20 José María Alonso
2017-10-28 14:11 José María Alonso
2017-10-07 15:16 José María Alonso
2017-10-01 21:20 José María Alonso
2017-10-01 18:50 José María Alonso
2017-04-05  8:24 José María Alonso
2017-04-05  8:18 José María Alonso
2017-02-14 23:06 José María Alonso
2017-02-14 23:00 José María Alonso
2017-02-14 22:08 José María Alonso
2017-02-14 22:01 José María Alonso
2017-02-14 22:01 José María Alonso
2017-01-16 10:27 José María Alonso
2017-01-11 22:15 José María Alonso
2017-01-11  9:25 José María Alonso
2016-06-11 16:44 Agostino Sarubbo
2016-03-24 14:59 José María Alonso
2015-10-18 15:51 José María Alonso
2015-08-27 20:08 José María Alonso

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=1643310397.1d2fc5b17044e43102a943874e230f67d0a4bb23.sam@gentoo \
    --to=sam@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