From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: www-client/badwolf/
Date: Mon, 27 Apr 2020 07:02:08 +0000 (UTC) [thread overview]
Message-ID: <1587940752.d57c1763fd27d27ae58b47ac3933bd1314ed192b.andrewammerlaan@gentoo> (raw)
commit: d57c1763fd27d27ae58b47ac3933bd1314ed192b
Author: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sun Apr 26 22:30:36 2020 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Sun Apr 26 22:39:12 2020 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=d57c1763
www-client/badwolf: longdescription lang="en"
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>
www-client/badwolf/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www-client/badwolf/metadata.xml b/www-client/badwolf/metadata.xml
index 5ee3f8f..102bfc5 100644
--- a/www-client/badwolf/metadata.xml
+++ b/www-client/badwolf/metadata.xml
@@ -5,7 +5,7 @@
<email>contact@hacktivis.me</email>
<name>Haelwenn (lanodan) Monnier</name>
</maintainer>
- <longdescription>
+ <longdescription lang="en">
BadWolf is a privacy-oriented WebKitGTK browser that doesn’t do compromises
for first-usage usability. Privacy is the first goal, and it should be
usable (security=usability^(-1) being false).
next reply other threads:[~2020-04-27 7:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 7:02 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-02 16:36 [gentoo-commits] repo/proj/guru:master commit in: www-client/badwolf/ Julien Roy
2024-03-09 1:19 David Roman
2024-02-28 7:19 Florian Schmaus
2023-09-21 10:09 David Roman
2023-08-24 22:41 [gentoo-commits] repo/proj/guru:dev " David Roman
2023-08-24 22:41 ` [gentoo-commits] repo/proj/guru:master " David Roman
2023-07-20 8:36 Florian Schmaus
2022-05-24 17:53 Haelwenn Monnier
2021-10-03 6:55 Arthur Zamarin
2021-10-02 8:43 Arthur Zamarin
2021-04-20 9:43 Andrew Ammerlaan
2021-04-20 9:43 Andrew Ammerlaan
2021-04-02 21:20 [gentoo-commits] repo/proj/guru:dev " Haelwenn Monnier
2021-04-03 0:03 ` [gentoo-commits] repo/proj/guru:master " Haelwenn Monnier
2021-04-02 20:24 Andrew Ammerlaan
2020-09-04 11:01 Andrew Ammerlaan
2020-07-21 13:53 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-07-21 13:53 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-07-09 14:29 Andrew Ammerlaan
2020-07-09 14:29 Andrew Ammerlaan
2020-05-18 9:09 Andrew Ammerlaan
2020-05-18 9:09 Andrew Ammerlaan
2020-04-05 11:01 Andrew Ammerlaan
2020-03-31 9:07 Andrew Ammerlaan
2020-03-31 9:07 Andrew Ammerlaan
2019-12-30 23:26 Ralph Seichter
2019-12-14 23:22 Ralph Seichter
2019-12-14 23:22 Ralph Seichter
2019-12-02 2:10 Ralph Seichter
2019-12-02 2:10 Ralph Seichter
2019-11-30 19:52 Ralph Seichter
2019-11-25 15:32 Ralph Seichter
2019-07-05 18:07 Ralph Seichter
2019-07-05 18:07 Ralph Seichter
2019-06-21 12:16 Ralph Seichter
2019-06-21 12:16 Ralph Seichter
2019-06-21 12:16 Ralph Seichter
2019-05-17 15:19 Ralph Seichter
2019-04-27 11:14 Ralph Seichter
2019-04-27 11:14 Ralph Seichter
2019-04-27 11:14 Ralph Seichter
2019-04-27 11:14 Ralph Seichter
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=1587940752.d57c1763fd27d27ae58b47ac3933bd1314ed192b.andrewammerlaan@gentoo \
--to=andrewammerlaan@riseup.net \
--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