From: "Viorel Munteanu" <ceamac@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: app-misc/Clipboard/
Date: Sun, 14 May 2023 07:44:50 +0000 (UTC) [thread overview]
Message-ID: <1684031146.e260aa8dcb4360eb28c6117334bf66b515904c6f.ceamac@gentoo> (raw)
commit: e260aa8dcb4360eb28c6117334bf66b515904c6f
Author: Quincy Fleming <quincyf467 <AT> protonmail <DOT> com>
AuthorDate: Sun May 14 02:25:46 2023 +0000
Commit: Viorel Munteanu <ceamac <AT> gentoo <DOT> org>
CommitDate: Sun May 14 02:25:46 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e260aa8d
app-misc/Clipboard: not new
Signed-off-by: Quincy Fleming <quincyf467 <AT> protonmail.com>
app-misc/Clipboard/metadata.xml | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/app-misc/Clipboard/metadata.xml b/app-misc/Clipboard/metadata.xml
new file mode 100644
index 000000000..0f4bbcf12
--- /dev/null
+++ b/app-misc/Clipboard/metadata.xml
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="person" proxied="yes">
+ <email>quincyf467@protonmail.com</email>
+ <name>Quincy Fleming</name>
+ </maintainer>
+ <maintainer type="project" proxied="proxy">
+ <email>proxy-maint@gentoo.org</email>
+ <name>Proxy Maintainers</name>
+ </maintainer>
+ <use>
+ <flag name="lto">Enable Link Time Optimization (LTO)</flag>
+ </use>
+ <upstream>
+ <remote-id type="github">Slackadays/Clipboard</remote-id>
+ <doc lang="en">https://github.com/Slackadays/Clipboard/blob/main/README.md</doc>
+ <bugs-to>https://github.com/Slackadays/Clipboard/issues</bugs-to>
+ </upstream>
+ <longdescription lang="en">
+ CB (or Clipboard) is a ridonkulously easy-to-use data remembrance tool bursting with oodles of useful features and absolutely gorgeous eye candy.
+
+ That's underselling it a bit.
+
+ This is your one-way golden ticket to saving time and effort anytime and anywhere. Have a telepath with an infallible memory always by your side. Feel the sheer power flowing through your commanding body as you cut, copy, paste, add, remove, load, and make note of anything that dares lay in your terminal at the mere press of a button. In no time, you'll be reclined back on a sunny beach in the Caribbean sipping a succulent papaya smoothie with the love of your life all while you watch dolphins leaping from the shimmering waves of the soft blue water. Ok, so maybe that last part won't actually happen, but you get the idea
+ </longdescription>
+</pkgmetadata>
next reply other threads:[~2023-05-14 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 7:44 Viorel Munteanu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 2:21 [gentoo-commits] repo/proj/guru:master commit in: app-misc/Clipboard/ Haelwenn Monnier
2023-10-03 9:34 [gentoo-commits] repo/proj/guru:master commit in: app-misc/clipboard/ David Roman
2023-12-17 23:08 David Roman
2023-12-20 9:10 David Roman
2024-05-15 19:13 Julien Roy
2024-11-09 16:30 Viorel Munteanu
2024-11-09 16:30 Viorel Munteanu
2024-11-12 13:20 David Roman
2024-11-18 4:59 Haelwenn Monnier
2024-11-18 4:59 Haelwenn Monnier
2024-11-27 16:35 Julien Roy
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=1684031146.e260aa8dcb4360eb28c6117334bf66b515904c6f.ceamac@gentoo \
--to=ceamac@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