From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-shells/fzf/
Date: Sun, 7 Jun 2020 12:12:35 +0000 (UTC) [thread overview]
Message-ID: <1591531940.9a2cbf7feaca7cd6fb7ad33816eda2532ccf05ff.juippis@gentoo> (raw)
commit: 9a2cbf7feaca7cd6fb7ad33816eda2532ccf05ff
Author: Olaf Torvaldsson <consus <AT> ftml <DOT> net>
AuthorDate: Wed May 27 20:10:20 2020 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sun Jun 7 12:12:20 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a2cbf7f
app-shells/fzf: remove long package description
Current description is rendered poorly on https://packages.gentoo.org
because parser does not care about hardcoded line breaks and squashes
the whole thing into one giant paragraph. The rest of the long
description is basically the same thing that we have in ebuild.
So nuke the longdescription field from metadata.xml.
Signed-off-by: Olaf Torvaldsson <consus <AT> ftml.net>
Closes: https://github.com/gentoo/gentoo/pull/15989
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
app-shells/fzf/metadata.xml | 23 -----------------------
1 file changed, 23 deletions(-)
diff --git a/app-shells/fzf/metadata.xml b/app-shells/fzf/metadata.xml
index 55c90b89b4e..aec0ee8918a 100644
--- a/app-shells/fzf/metadata.xml
+++ b/app-shells/fzf/metadata.xml
@@ -13,29 +13,6 @@
<email>proxy-maint@gentoo.org</email>
<name>Proxy Maintainers</name>
</maintainer>
- <longdescription>
- fzf is a general-purpose command-line fuzzy finder. It's an interactive Unix filter for command-line
- that can be used with any list; files, command history, processes, hostnames, bookmarks, git commits, etc.
- Fuzzy completion for files and directories can be triggered if the word before the cursor ends with the
- trigger sequence which is by default **.
- To use the fzf key-binding for your shell, make sure to source the right file for your shell
- from /usr/share/fzf/
-
- For bash, add the following line to ~/.bashrc
- # source /usr/share/fzf/fzf.sh
-
- Or symlink the fzf bash script
- # ln -s /usr/share/fzf/fzf.sh /etc/bash/bashrc.d/fzf.sh
-
- For fish, make sure to symlink the file
- # ln -s /usr/share/fzf/fzf.fish /usr/share/fish/functions/fzf.fish
-
- For zsh, make sure to symlink the file
- # ln -s /usr/share/fzf/fzf.fish /usr/share/zsh/site-contrib/fzf.fish
-
- Or add the following line to your ~/.zshrc
- # source /usr/share/fzf/fzf.zsh
- </longdescription>
<stabilize-allarches/>
<upstream>
<remote-id type="github">junegunn/fzf</remote-id>
next reply other threads:[~2020-06-07 12:12 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 12:12 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 16:47 [gentoo-commits] repo/gentoo:master commit in: app-shells/fzf/ Arthur Zamarin
2024-11-04 3:28 Sam James
2024-11-04 3:05 Sam James
2024-11-04 1:26 Matt Turner
2024-09-24 0:36 Matt Turner
2024-09-05 0:06 Sam James
2024-09-02 19:25 Sam James
2024-09-02 19:25 Sam James
2024-09-02 18:22 Matt Turner
2024-07-31 16:14 Matt Turner
2024-07-31 16:14 Matt Turner
2024-07-22 10:29 Jakov Smolić
2024-07-22 5:43 Joonas Niilola
2024-07-22 5:43 Joonas Niilola
2024-07-22 3:27 Matt Turner
2024-07-15 18:05 Matt Turner
2024-07-02 9:48 Sam James
2024-07-02 5:48 Joonas Niilola
2024-07-02 5:45 Joonas Niilola
2024-06-11 19:09 Matt Turner
2024-06-11 19:09 Matt Turner
2024-06-06 4:05 Sam James
2024-06-06 1:55 Jakov Smolić
2024-06-06 0:45 Sam James
2024-05-16 6:52 Joonas Niilola
2024-05-16 6:52 Joonas Niilola
2024-05-16 4:17 Arthur Zamarin
2024-05-15 15:29 Matt Turner
2024-05-01 20:24 Matt Turner
2024-04-10 17:17 Matt Turner
2024-02-27 23:00 Sam James
2024-02-02 1:18 Sam James
2024-02-02 1:02 Sam James
2024-01-28 21:51 Sam James
2024-01-28 20:36 Jonas Stein
2024-01-02 7:27 Sam James
2023-12-16 7:05 Arthur Zamarin
2023-12-16 4:12 Sam James
2023-11-25 22:47 Sam James
2023-11-25 22:47 Sam James
2023-11-13 3:28 Sam James
2023-10-15 8:26 Sam James
2023-08-29 7:01 Sam James
2023-07-16 17:34 Arthur Zamarin
2023-07-16 17:34 Arthur Zamarin
2023-06-15 22:03 Sam James
2023-05-27 7:07 Sam James
2023-05-27 7:07 Sam James
2023-05-27 7:07 Sam James
2023-05-26 12:52 Sam James
2023-05-01 15:00 Sam James
2023-05-01 15:00 Sam James
2023-05-01 10:42 Sam James
2023-04-02 21:44 Sam James
2023-02-16 4:18 Sam James
2023-02-12 6:22 Sam James
2023-01-26 8:30 Joonas Niilola
2023-01-26 8:30 Joonas Niilola
2023-01-26 7:15 Sam James
2023-01-25 7:13 Sam James
2023-01-17 1:53 Sam James
2023-01-17 1:53 Sam James
2022-11-19 3:23 Sam James
2022-11-11 22:36 Sam James
2022-11-09 12:30 Matt Turner
2022-11-05 17:11 Agostino Sarubbo
2022-11-05 6:27 Sam James
2022-09-29 5:10 Joonas Niilola
2022-09-29 5:10 Joonas Niilola
2022-09-28 23:35 Sam James
2022-08-29 20:13 Sam James
2022-08-29 19:06 Sam James
2022-08-12 18:16 Sam James
2022-07-22 22:02 Sam James
2022-07-19 19:47 Matt Turner
2022-07-12 6:47 Agostino Sarubbo
2022-07-12 6:46 Agostino Sarubbo
2022-06-05 5:28 Joonas Niilola
2022-06-05 5:28 Joonas Niilola
2022-06-04 19:46 Matt Turner
2022-06-04 19:46 Matt Turner
2022-02-02 22:24 Sam James
2022-02-02 22:24 Sam James
2022-01-12 9:31 Georgy Yakovlev
2022-01-02 13:26 Georgy Yakovlev
2022-01-02 13:21 Yixun Lan
2021-11-14 5:25 Sam James
2021-11-14 5:25 Sam James
2021-11-11 9:47 Jakov Smolić
2021-11-11 8:36 Jakov Smolić
2021-11-04 17:09 Sam James
2021-07-13 0:05 Sam James
2021-07-12 22:37 Sam James
2021-06-16 14:14 Sam James
2021-06-16 14:14 Sam James
2021-06-16 14:14 Sam James
2021-06-16 14:14 Sam James
2021-05-10 6:14 Joonas Niilola
2021-02-09 8:35 Sam James
2021-02-09 8:35 Sam James
2021-01-09 4:21 Sam James
2021-01-09 4:21 Sam James
2020-12-16 8:29 Joonas Niilola
2020-10-31 9:47 Joonas Niilola
2020-10-31 9:47 Joonas Niilola
2020-08-12 7:23 Joonas Niilola
2020-05-27 6:18 Joonas Niilola
2020-04-29 11:40 Joonas Niilola
2020-04-23 6:37 Joonas Niilola
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=1591531940.9a2cbf7feaca7cd6fb7ad33816eda2532ccf05ff.juippis@gentoo \
--to=juippis@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