From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emacs/ruby-mode/
Date: Sun, 17 Apr 2022 08:35:30 +0000 (UTC) [thread overview]
Message-ID: <1650184487.8e6d59d0709eabb243dc51dc0dd7e95703a15d87.sam@gentoo> (raw)
commit: 8e6d59d0709eabb243dc51dc0dd7e95703a15d87
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 17 08:34:07 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 17 08:34:47 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8e6d59d0
app-emacs/ruby-mode: Stabilize 3.0.0 ALLARCHES, #838904
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-emacs/ruby-mode/ruby-mode-3.0.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-emacs/ruby-mode/ruby-mode-3.0.0.ebuild b/app-emacs/ruby-mode/ruby-mode-3.0.0.ebuild
index 2424af40dc80..b17719e6586f 100644
--- a/app-emacs/ruby-mode/ruby-mode-3.0.0.ebuild
+++ b/app-emacs/ruby-mode/ruby-mode-3.0.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/ruby/elisp/archive/${COMMIT}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-3+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos"
+KEYWORDS="~alpha amd64 arm ~hppa ~ia64 ppc ppc64 ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos"
S="${WORKDIR}/elisp-${COMMIT}"
DOCS="README"
next reply other threads:[~2022-04-17 8:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 8:35 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 21:30 [gentoo-commits] repo/gentoo:master commit in: app-emacs/ruby-mode/ Sam James
2022-04-17 9:42 Ulrich Müller
2021-03-08 10:25 Sam James
2021-03-08 9:56 Hans de Graaff
2021-03-08 9:56 Hans de Graaff
2021-01-06 13:07 Fabian Groffen
2019-12-26 11:06 Hans de Graaff
2019-12-12 9:37 Agostino Sarubbo
2019-12-10 12:19 Agostino Sarubbo
2019-12-10 8:57 Agostino Sarubbo
2019-12-10 8:56 Agostino Sarubbo
2019-12-10 8:54 Agostino Sarubbo
2019-12-09 13:10 Agostino Sarubbo
2019-12-08 23:37 Sergei Trofimovich
2019-11-18 12:32 Ulrich Müller
2019-10-05 6:54 Michał Górny
2019-07-09 17:23 Hans de Graaff
2019-07-09 9:32 Agostino Sarubbo
2019-07-09 9:31 Agostino Sarubbo
2019-07-05 10:13 Agostino Sarubbo
2019-07-05 8:49 Agostino Sarubbo
2019-07-05 8:42 Agostino Sarubbo
2019-07-05 8:41 Agostino Sarubbo
2019-07-05 8:38 Agostino Sarubbo
2019-07-05 4:45 Hans de Graaff
2019-07-05 4:45 Hans de Graaff
2019-07-05 4:45 Hans de Graaff
2019-01-11 8:23 Hans de Graaff
2019-01-11 8:23 Hans de Graaff
2018-08-04 5:57 Hans de Graaff
2018-08-04 5:57 Hans de Graaff
2018-04-08 22:11 Matt Turner
2018-03-21 1:38 Matt Turner
2018-03-18 19:59 Markus Meier
2018-03-14 21:29 Sergei Trofimovich
2018-03-14 8:03 Sergei Trofimovich
2018-02-18 11:28 Sergei Trofimovich
2018-01-23 23:01 Sergei Trofimovich
2018-01-21 20:30 Thomas Deutschmann
2018-01-21 15:47 Hans de Graaff
2017-07-11 4:58 Markus Meier
2017-06-05 21:53 Sergei Trofimovich
2017-04-25 7:08 Tobias Klausmann
2017-03-29 5:21 Hans de Graaff
2017-01-29 14:49 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=1650184487.8e6d59d0709eabb243dc51dc0dd7e95703a15d87.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