From: Marc MERLIN <marc@merlins.org>
To: Filipe Manana <fdmanana@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix csum tree corruption, duplicate and outdated checksums
Date: Sat, 9 Aug 2014 13:10:51 -0700 [thread overview]
Message-ID: <20140809201051.GJ12778@merlins.org> (raw)
In-Reply-To: <1407615747-12949-1-git-send-email-fdmanana@suse.com>
On Sat, Aug 09, 2014 at 09:22:27PM +0100, Filipe Manana wrote:
(100 lines of detailled explanations snipped)
> - slot = 0;
> + slot = path->slots[0];
And this is why, trying to rank kernel contributions by number of
lines or characters is a very poor guide of the actual work accomplished
and owed credit.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next prev parent reply other threads:[~2014-08-09 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 20:22 [PATCH] Btrfs: fix csum tree corruption, duplicate and outdated checksums Filipe Manana
2014-08-09 19:40 ` Josef Bacik
2014-08-09 20:10 ` Marc MERLIN [this message]
2014-08-09 20:25 ` Chris Mason
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=20140809201051.GJ12778@merlins.org \
--to=marc@merlins.org \
--cc=fdmanana@suse.com \
--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).