[
Date Prev
][
Date Next
] [
Thread Prev
][
Thread Next
] [
Date Index
] [
Thread Index
]
Bug#956596: use original gem instead of gitlab's fork
To
:
956596@bugs.debian.org
Subject
: Bug#956596: use original gem instead of gitlab's fork
From
: Pirate Praveen <
praveen@onenetbeyond.org
>
Date
: Mon, 13 Apr 2020 17:18:19 +0530
Message-id
: <
[🔎]
J46Q8Q.BJT6OWK92ECU@onenetbeyond.org
>
Reply-to
: Pirate Praveen <
praveen@onenetbeyond.org
>,
956596@bugs.debian.org
References
: <
[🔎]
TR5Q8Q.8MSJ2U4Y8EGF2@onenetbeyond.org
>
Control: retitle -1 ITP: ruby-derailed-benchmarks -- Benchmarks
designed to performance test your ENTIRE site
From
https://rubygems.org/gems/derailed_benchmarks
Reply to:
debian-wnpp@lists.debian.org
Pirate Praveen (on-list)
Pirate Praveen (off-list)
References
:
Bug#956596: ITP: ruby-gitlab-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site
From:
Pirate Praveen <praveen@onenetbeyond.org>
Prev by Date:
Bug#956596: ITP: ruby-gitlab-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site
Next by Date:
Processed: use original gem instead of gitlab's fork
Previous by thread:
Bug#956596: ITP: ruby-gitlab-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site
Next by thread:
Processed: use original gem instead of gitlab's fork
Index(es):
Date
Thread