public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-accessibility/brltty/
Date: Sun, 11 Aug 2019 11:20:41 +0000 (UTC)	[thread overview]
Message-ID: <1565522355.9b88b79823018a4c084e1450d9a41088571d6cb3.soap@gentoo> (raw)

commit:     9b88b79823018a4c084e1450d9a41088571d6cb3
Author:     David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 11 11:19:15 2019 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sun Aug 11 11:19:15 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b88b798

app-accessibility/brltty: [QA] Fix missing trailing slash

Package-Manager: Portage-2.3.71, Repoman-2.3.17
Signed-off-by: David Seifert <soap <AT> gentoo.org>

 app-accessibility/brltty/brltty-6.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-accessibility/brltty/brltty-6.0-r1.ebuild b/app-accessibility/brltty/brltty-6.0-r1.ebuild
index 82168179665..34d65bbe543 100644
--- a/app-accessibility/brltty/brltty-6.0-r1.ebuild
+++ b/app-accessibility/brltty/brltty-6.0-r1.ebuild
@@ -208,7 +208,7 @@ src_install() {
 
 pkg_postinst() {
 	elog
-	elog "please be sure ${ROOT}etc/brltty.conf is correct for your system."
+	elog "please be sure ${ROOT}/etc/brltty.conf is correct for your system."
 	elog
 	elog "To make brltty start on boot, type this command as root:"
 	elog


             reply	other threads:[~2019-08-11 11:20 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 11:20 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-17 17:46 [gentoo-commits] repo/gentoo:master commit in: app-accessibility/brltty/ Andreas Sturmlechner
2024-08-09 10:35 Pacho Ramos
2024-08-09 10:35 Pacho Ramos
2024-06-02  8:19 Sam James
2024-02-28 14:04 Michał Górny
2024-01-11  9:38 Sam James
2023-12-29 19:04 Arthur Zamarin
2023-12-25  8:19 Sam James
2023-12-25  7:30 Sam James
2023-12-16 10:59 Arthur Zamarin
2023-12-16 10:59 Arthur Zamarin
2023-12-16  9:10 Sam James
2023-11-29  4:10 Sam James
2023-11-29  4:10 Sam James
2023-11-29  4:10 Sam James
2023-10-13  2:44 Sam James
2023-08-25 22:21 Sam James
2023-01-26  4:40 Sam James
2023-01-26  4:40 Sam James
2022-11-07  8:11 Sam James
2022-11-07  7:08 Sam James
2022-11-06 19:06 Sam James
2022-11-06  7:41 Sam James
2022-10-02  4:42 William Hubbs
2022-10-01  3:55 Sam James
2022-05-26  5:30 WANG Xuerui
2022-03-09 23:46 Sam James
2022-03-07  3:47 Sam James
2022-03-02  9:08 Agostino Sarubbo
2022-03-01 11:42 Jakov Smolić
2022-03-01 11:29 Agostino Sarubbo
2022-03-01 11:28 Agostino Sarubbo
2022-02-15 18:31 Matt Turner
2022-01-31  2:36 Yixun Lan
2022-01-29 22:23 William Hubbs
2022-01-29 22:13 William Hubbs
2022-01-29 19:26 William Hubbs
2022-01-29  7:10 Sam James
2022-01-28 18:50 William Hubbs
2022-01-28 18:45 William Hubbs
2022-01-28 17:24 William Hubbs
2022-01-28  9:32 Agostino Sarubbo
2022-01-24 21:09 Agostino Sarubbo
2022-01-24 14:47 Sam James
2022-01-24 14:42 Sam James
2022-01-24  8:17 Agostino Sarubbo
2021-12-01  6:37 Yixun Lan
2021-10-31  3:06 Sam James
2021-04-19  2:10 Matt Turner
2021-04-03 18:28 Mike Gilbert
2020-08-19 22:40 Sam James
2020-08-16  7:52 Mart Raudsepp
2020-05-11 16:49 Agostino Sarubbo
2020-05-09  7:40 Agostino Sarubbo
2020-05-06  7:18 Sergei Trofimovich
2020-05-03 21:55 Sergei Trofimovich
2020-04-19  8:15 Mart Raudsepp
2020-03-20 21:53 Matt Turner
2020-02-10 20:32 Michał Górny
2019-08-03 13:14 Aaron Bauman
2019-05-19  0:09 Michael Palimaka
2019-03-27 15:21 Lars Wendler
2019-03-27 15:03 Lars Wendler
2018-09-28  9:45 Matt Turner
2017-12-09 14:21 Pacho Ramos
2017-04-19  8:03 David Seifert
2016-05-06 22:11 William Hubbs
2015-11-09 21:51 Pacho Ramos

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=1565522355.9b88b79823018a4c084e1450d9a41088571d6cb3.soap@gentoo \
    --to=soap@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