From: Shinobu Kinjo <skinjo@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Documentations (ceph/doc/dev)
Date: Tue, 29 Mar 2016 19:56:19 -0400 (EDT) [thread overview]
Message-ID: <1809652512.76865295.1459295779722.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56FB1592.2040606@dachary.org>
Hi,
I was asking because they are pretty much useful.
Cheers,
S
----- Original Message -----
From: "Loic Dachary" <loic@dachary.org>
To: "Shinobu Kinjo" <skinjo@redhat.com>, "Ceph Devel" <ceph-devel@vger.kernel.org>
Sent: Wednesday, March 30, 2016 8:53:54 AM
Subject: Re: Documentations (ceph/doc/dev)
Hi,
On 30/03/2016 01:36, Shinobu Kinjo wrote:
> Hi,
>
> Are documentations in ceph/doc/dev@github well-maintained?
http://docs.ceph.com/docs/master/dev/
There has been a steady flow of improvements in the past few months. And currently one pull request being reviewed at https://github.com/ceph/ceph/pull/8358. It could be better I'm sure but it's definitely maintained ;-)
Cheers
>
> Cheers,
> Shinobu
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-29 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <826327531.76855144.1459294311036.JavaMail.zimbra@redhat.com>
2016-03-29 23:36 ` Documentations (ceph/doc/dev) Shinobu Kinjo
2016-03-29 23:53 ` Loic Dachary
2016-03-29 23:56 ` Shinobu Kinjo [this message]
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=1809652512.76865295.1459295779722.JavaMail.zimbra@redhat.com \
--to=skinjo@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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 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.