From: Philippe Loctaux <phil@philippeloctaux.com>
To: Filipe Manana <fdmanana@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [Question]: Contributing to btrfs
Date: Mon, 22 Feb 2016 17:45:21 +0100 [thread overview]
Message-ID: <20160222164521.GC2267@carbon.home> (raw)
In-Reply-To: <CAL3q7H7hhaDQ3e2oCW96iwr6NPww-57e9b675oQ-MY6EVTrVQA@mail.gmail.com>
On Mon, Feb 22, 2016 at 01:29:31PM +0000, Filipe Manana wrote:
> Whitespace/style patches I doubt. He probably encourages for small
> cleanup/optimizations as the first patch, like he did recently at
> https://lkml.org/lkml/2015/9/15/919. That's something that requires
> some thinking and understanding. Now running checkpatch and fix its
> warnings, doesn't require any skill at all.
> What were you planning? Sending more 100 patches, each one to fix a
> different style issue for each function? There's probably hundreds or
> thousands more style/whitespace "issues" to fix in btrfs alone.
I agree with you, I won't spend all my time fixing style/whitespace
issues, now that I know what I can do, thanks for that :)
--
Philippe Loctaux
phil@philippeloctaux.com
next prev parent reply other threads:[~2016-02-22 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 21:09 [Question]: Contributing to btrfs Philippe Loctaux
2016-02-20 22:40 ` Philippe Loctaux
2016-02-21 6:14 ` Duncan
2016-02-22 1:18 ` Qu Wenruo
2016-02-22 7:26 ` Philippe Loctaux
2016-02-22 7:34 ` Qu Wenruo
2016-02-22 7:42 ` Philippe Loctaux
2016-02-22 10:47 ` Filipe Manana
2016-02-22 12:02 ` Simon Quigley
2016-02-22 13:29 ` Filipe Manana
2016-02-22 14:45 ` Simon Quigley
2016-02-23 1:32 ` Qu Wenruo
2016-02-23 2:07 ` Simon Quigley
2016-02-23 2:20 ` Qu Wenruo
2016-02-22 16:45 ` Philippe Loctaux [this message]
2016-02-22 12:18 ` David Sterba
2016-02-22 16:41 ` Philippe Loctaux
2016-02-22 17:15 ` David Sterba
2016-02-22 11:34 ` David Sterba
2016-02-22 16:38 ` Philippe Loctaux
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=20160222164521.GC2267@carbon.home \
--to=phil@philippeloctaux.com \
--cc=fdmanana@gmail.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).