From: Martin Steigerwald <Martin@lichtvoll.de>
To: Hugo Mills <hugo@carfax.org.uk>,
Nick Krause <xerofoify@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Help with Project on brtfs wiki
Date: Sat, 26 Jul 2014 12:32:30 +0200 [thread overview]
Message-ID: <2011812.fBpMKCudf2@merkaba> (raw)
In-Reply-To: <20140726100503.GF31950@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Hi Hugo,
Am Samstag, 26. Juli 2014, 11:05:03 schrieb Hugo Mills:
> > I am not asking to hold my hand
>
> You are, though. Something like using grep to find code that (might
> be) related to the thing you're trying to work with is _fundamental_.
> You should expect to be reading the code -- several layers deep, in
> both directions from any given function -- in order to understand what
> it does and how it fits in, and what problems you might enncounter if
> you change it. If you won't put in that degree of basic effort, then
> you won't get very far.
Actually, from what I read from Nick Krause so far here and on LKML:
Can it be that he is at admittedly quite inventive trolling?
I found none of his posts to be even remotely convincing although he submitted
a patch elsewhere.
Thanks for your detailed explaination tough.
To Nick: If I am mistaken – mea culpa. But your posts just seem to follow what
I perceive the usual style of something into trolling.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-07-26 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 23:16 Help with Project on brtfs wiki Nick Krause
2014-07-26 10:05 ` Hugo Mills
2014-07-26 10:32 ` Martin Steigerwald [this message]
2014-07-26 11:07 ` Wang Shilong
2014-07-27 1:43 ` Nick Krause
2014-07-27 2:05 ` Chris Murphy
2014-07-27 2:14 ` Nick Krause
2014-07-27 2:15 ` Eric Sandeen
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=2011812.fBpMKCudf2@merkaba \
--to=martin@lichtvoll.de \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=xerofoify@gmail.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