From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-protection/
Date: Tue, 13 Jun 2023 10:11:16 +0000 (UTC) [thread overview]
Message-ID: <1686651073.79bba396560e8527ea6ea4d63c04f4776caa02fb.graaff@gentoo> (raw)
commit: 79bba396560e8527ea6ea4d63c04f4776caa02fb
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 13 10:10:58 2023 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Tue Jun 13 10:11:13 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79bba396
dev-ruby/rack-protection: update upstream metadata
Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>
dev-ruby/rack-protection/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/rack-protection/metadata.xml b/dev-ruby/rack-protection/metadata.xml
index 2ca187126bb2..f2a92a716a0a 100644
--- a/dev-ruby/rack-protection/metadata.xml
+++ b/dev-ruby/rack-protection/metadata.xml
@@ -10,6 +10,6 @@
of software inbetween.
</longdescription>
<upstream>
- <remote-id type="github">rkh/rack-protection</remote-id>
+ <remote-id type="github">sinatra/rack-protection</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-06-13 10:11 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 10:11 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 14:27 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rack-protection/ Sam James
2024-07-14 8:48 Hans de Graaff
2024-07-14 7:48 Hans de Graaff
2024-05-28 4:54 Hans de Graaff
2024-05-28 4:54 Hans de Graaff
2024-01-21 7:45 Hans de Graaff
2023-12-29 7:40 Hans de Graaff
2023-08-19 5:25 Hans de Graaff
2023-08-12 7:21 Hans de Graaff
2023-07-24 12:07 Jakov Smolić
2023-06-13 10:11 Hans de Graaff
2023-06-13 10:11 Hans de Graaff
2023-04-07 11:25 Sam James
2023-04-07 4:12 Sam James
2023-01-08 7:49 Hans de Graaff
2023-01-08 7:49 Hans de Graaff
2022-12-04 17:56 Arthur Zamarin
2022-12-03 11:04 Hans de Graaff
2022-10-22 4:36 Hans de Graaff
2022-10-01 7:55 Hans de Graaff
2022-07-24 7:38 Hans de Graaff
2022-07-16 6:53 Hans de Graaff
2022-06-04 5:47 Hans de Graaff
2022-05-06 8:22 Hans de Graaff
2022-05-06 8:22 Hans de Graaff
2022-03-18 6:57 Hans de Graaff
2021-09-07 21:28 Marek Szuba
2021-05-22 7:21 Hans de Graaff
2020-12-29 10:48 Hans de Graaff
2020-12-29 7:21 Hans de Graaff
2020-09-19 6:06 Hans de Graaff
2020-09-05 8:01 Hans de Graaff
2020-07-05 6:27 Hans de Graaff
2020-06-21 9:05 Hans de Graaff
2020-03-12 13:47 Hans de Graaff
2020-03-01 8:22 Hans de Graaff
2019-08-24 4:45 Hans de Graaff
2019-04-27 6:13 Hans de Graaff
2019-04-27 6:13 Hans de Graaff
2019-01-11 7:59 Hans de Graaff
2018-12-24 7:04 Hans de Graaff
2018-09-27 4:11 Hans de Graaff
2018-07-19 6:30 Hans de Graaff
2018-07-18 5:51 Hans de Graaff
2018-07-18 5:51 Hans de Graaff
2018-07-18 5:51 Hans de Graaff
2018-07-18 5:51 Hans de Graaff
2018-07-06 4:15 Hans de Graaff
2018-06-07 4:43 Hans de Graaff
2018-04-27 8:33 Hans de Graaff
2018-02-19 6:18 Hans de Graaff
2017-06-30 11:17 Alexis Ballier
2017-06-23 3:38 Hans de Graaff
2017-06-12 6:04 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-07-25 17:28 Hans de Graaff
2016-06-02 21:48 Richard Farina
2016-04-16 5:59 Hans de Graaff
2015-08-16 23:14 Mikle Kolyada
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=1686651073.79bba396560e8527ea6ea4d63c04f4776caa02fb.graaff@gentoo \
--to=graaff@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