From: Jeff Wu <cpwu@tnsoft.com.cn>
To: Sage Weil <sage@newdream.net>
Cc: "gregf@hq.newdream.net" <gregf@hq.newdream.net>,
"yehuda@hq.newdream.net" <yehuda@hq.newdream.net>,
"colinm@hq.newdream.net" <colinm@hq.newdream.net>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Andrew Lv <mllv@tnsoft.com.cn>, Kevin Chen <wchen@tnsoft.com.cn>
Subject: Re: [BUG] ceph 0.23 ,sudo /etc/init.d/init-ceph cleanalllogs , delete / folder
Date: Mon, 6 Dec 2010 13:55:08 +0800 [thread overview]
Message-ID: <1291614908.3788.5.camel@cephhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1012030919330.1982@cobra.newdream.net>
在 2010-12-04六的 01:20 +0800，Sage Weil写道：
> On Fri, 3 Dec 2010, Jeff Wu wrote:
> > > Yes, please. You can create an account, log in, and then click the 'new
> > > issue' button along the top. In this case the issue is fixed for the next
> > > release though (I believe?) so we should be okay.
> > >
> > Hi, if i create a new issue ,who should the bug be assigned to ?
>
> In the cleanlogs case, no need to enter a bug, as it's fixed in
> the 'rc' branch. In general for other bugs, just leave it unassigned.
>
Hi sage, i get it ,thank you.
> Thanks!
> sage
>
> >
> >
> >
> > > Thanks!
> > > sage
> >
> > --
> > 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
> >
> >
--
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:[~2010-12-06 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 7:25 [BUG] ceph 0.23 ,sudo /etc/init.d/init-ceph cleanalllogs , delete / folder Jeff Wu
2010-12-02 19:22 ` Sage Weil
2010-12-03 1:01 ` Jeff Wu
2010-12-03 1:22 ` Jeff Wu
2010-12-03 17:20 ` Sage Weil
2010-12-06 5:55 ` Jeff Wu [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=1291614908.3788.5.camel@cephhost \
--to=cpwu@tnsoft.com.cn \
--cc=ceph-devel@vger.kernel.org \
--cc=colinm@hq.newdream.net \
--cc=gregf@hq.newdream.net \
--cc=mllv@tnsoft.com.cn \
--cc=sage@newdream.net \
--cc=wchen@tnsoft.com.cn \
--cc=yehuda@hq.newdream.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox