Processed: use original gem instead of gitlab's fork

To: Pirate Praveen <praveen@onenetbeyond.org>
Cc: praveen@debian.org, wnpp@debian.org
Subject: Processed: use original gem instead of gitlab's fork
From: "Debian Bug Tracking System" <owner@bugs.debian.org>
Date: Mon, 13 Apr 2020 11:51:03 +0000
Message-id: <[🔎] handler.s.B956596.158677851330526.transcript@bugs.debian.org>
References: <[🔎] J46Q8Q.BJT6OWK92ECU@onenetbeyond.org> <[🔎] TR5Q8Q.8MSJ2U4Y8EGF2@onenetbeyond.org>

Processing control commands:

> retitle -1 ITP: ruby-derailed-benchmarks -- Benchmarks
Bug #956596 [wnpp] ITP: ruby-gitlab-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site
Changed Bug title to 'ITP: ruby-derailed-benchmarks -- Benchmarks' from 'ITP: ruby-gitlab-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site'.

-- 
956596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956596
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Reply to:

References:
- Bug#956596: use original gem instead of gitlab's fork
  - From: Pirate Praveen <praveen@onenetbeyond.org>
- 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: use original gem instead of gitlab's fork
Next by Date: Bug#947962:
Previous by thread: Bug#956596: use original gem instead of gitlab's fork
Next by thread: Bug#956596: marked as done (ITP: ruby-derailed-benchmarks -- Benchmarks designed to performance test your ENTIRE site)
Index(es):
- Date
- Thread