From: Loic Dachary <loic@dachary.org>
To: David Zafman <david.zafman@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Ceph man page is out of sync with actual command options
Date: Thu, 29 Jan 2015 11:44:13 +0100 [thread overview]
Message-ID: <54CA0EFD.40708@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi David,
I see you created a pull requests for backporting documentation to firefly https://github.com/ceph/ceph/pull/3521
And also three issues to track the backport on firefly, giant and future hammer:
http://tracker.ceph.com/issues/10676 http://tracker.ceph.com/issues/10677 http://tracker.ceph.com/issues/10678
I'm not sure why http://tracker.ceph.com/issues/10678 is necessary ?
Since there does not seem to be an issue associated with the man page updates being backported, I understand why you created http://tracker.ceph.com/issues/10676. I would have expected to see, in the backport field of this issue, the string "firefly,giant" to note that the intention is to backport to these releases. I think that's what we usually do for backporting. Is there a specific reason for creating http://tracker.ceph.com/issues/10677 ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2015-01-29 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54CA0EFD.40708@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=david.zafman@inktank.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.