From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V4 2/2] btrfs-progs: Introduce device delete by devid
Date: Thu, 10 Mar 2016 11:09:29 +0800 [thread overview]
Message-ID: <56E0E569.5010309@oracle.com> (raw)
In-Reply-To: <20160309165515.GA18908@suse.cz>
> Please send any followup changes on top of the current devel patch.
I kind of missed this point at the wiki.
--
The git repositories on kernel.org are not used for development
or integration branches.
--
Thanks for the update on how things work at your end, which helps
to keep loss of productive at low.
Suggest that we need to update similar for the kernel
section as well. I see some of the inactive branches
being mentioned there. And its bit confusing as of now.
-ASJ
next prev parent reply other threads:[~2016-03-10 3:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 9:33 [PATCH V3 2/2] btrfs-progs: Introduce device delete by devid Anand Jain
2016-02-18 16:49 ` David Sterba
2016-03-09 10:07 ` [PATCH V4 " Anand Jain
2016-03-09 10:10 ` Anand Jain
2016-03-09 16:55 ` David Sterba
2016-03-10 3:09 ` Anand Jain [this message]
2016-03-10 16:40 ` David Sterba
2016-03-14 17:48 ` Yauhen Kharuzhy
2016-03-14 18:36 ` David Sterba
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=56E0E569.5010309@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).