From: Anand Jain <Anand.Jain@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs and btrfs code similar why ?
Date: Fri, 14 Jun 2013 09:53:55 +0800 [thread overview]
Message-ID: <51BA77B3.7060706@oracle.com> (raw)
In-Reply-To: <51B94E47.1070900@redhat.com>
> Because they work with the same on-disk structures, and need
> to perform many of the same tasks. So using the same code base
> means bugs get fixed once, features get written once, there is
> built-in consistency, more coverage, etc.
yes. Thanks Eric.
- Anand
prev parent reply other threads:[~2013-06-14 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 3:56 btrfs-progs and btrfs code similar why ? Anand Jain
2013-06-13 4:44 ` Eric Sandeen
2013-06-14 1:53 ` Anand Jain [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=51BA77B3.7060706@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sandeen@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 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).