From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sjust@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Replacing Pending Backports with Backports in the Ceph bug queue - no subprojects
Date: Tue, 01 Sep 2015 23:24:27 +0200 [thread overview]
Message-ID: <55E6178B.8050501@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hi Sam,
I modified the http://tracker.ceph.com/projects/ceph/issues?query_id=47 "Bug queue - no subprojects" to not display the "Pending Backports" and include the "Backport" tracker instead. Now that there is a separate Backport tracker, the backporting activity that used to be logged in "Pending Backports" issues is now logged in the matching "Backport" issue(s) and that seemed more appropriate.
If you think this is not a good idea let me know and I'll revert.
Cheers
P.S. I know you're on vacation, this is a message for when you're back ;-)
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-09-01 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 21:24 Loic Dachary [this message]
2015-09-01 21:47 ` Replacing Pending Backports with Backports in the Ceph bug queue - no subprojects Sage Weil
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=55E6178B.8050501@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.