From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/childlabor/
Date: Fri, 24 Mar 2023 03:58:45 +0000 (UTC) [thread overview]
Message-ID: <1679627515.0f2d6eea046ecf53af2317d5b5da64e517fbf958.sam@gentoo> (raw)
commit: 0f2d6eea046ecf53af2317d5b5da64e517fbf958
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 24 03:11:55 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 24 03:11:55 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0f2d6eea
dev-ruby/childlabor: update DESCRIPTION
I think this was a copy/paste error from elsewhere.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/childlabor/childlabor-0.0.3-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/childlabor/childlabor-0.0.3-r2.ebuild b/dev-ruby/childlabor/childlabor-0.0.3-r2.ebuild
index f7c8a220b6eb..532a0b976d40 100644
--- a/dev-ruby/childlabor/childlabor-0.0.3-r2.ebuild
+++ b/dev-ruby/childlabor/childlabor-0.0.3-r2.ebuild
@@ -12,7 +12,7 @@ RUBY_FAKEGEM_GEMSPEC="childlabor.gemspec"
inherit ruby-fakegem
-DESCRIPTION="A scripting framework that replaces rake and sake"
+DESCRIPTION="Gem that helps manage child processes"
HOMEPAGE="https://github.com/carllerche/childlabor"
COMMIT_ID="6518b939dddbad20c7f05aa075d76e3ca6e70447"
SRC_URI="https://github.com/carllerche/childlabor/archive/${COMMIT_ID}.tar.gz -> ${P}.tar.gz"
next reply other threads:[~2023-03-24 3:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 3:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-02 3:56 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/childlabor/ Ionen Wolkens
2023-12-31 19:49 Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-03-18 0:02 Sam James
2022-08-14 6:24 Hans de Graaff
2022-06-28 16:59 Arthur Zamarin
2022-06-28 16:47 Arthur Zamarin
2022-05-08 15:00 WANG Xuerui
2022-04-27 4:34 Arthur Zamarin
2022-04-26 13:45 Sam James
2022-04-01 5:15 Arthur Zamarin
2022-01-15 6:43 Hans de Graaff
2022-01-15 6:29 Hans de Graaff
2021-11-24 12:46 Hans de Graaff
2021-10-02 20:40 Sam James
2021-08-11 14:29 Marek Szuba
2020-04-19 12:22 Sergei Trofimovich
2020-02-15 6:44 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-02-03 10:49 Hans de Graaff
2018-03-27 5:48 Hans de Graaff
2017-05-06 6:41 Hans de Graaff
2017-04-29 20:13 Jeroen Roovers
2016-11-27 8:01 Hans de Graaff
2016-09-28 8:17 Tobias Klausmann
2016-03-28 19:32 Manuel Rüger
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=1679627515.0f2d6eea046ecf53af2317d5b5da64e517fbf958.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