From: Ben Gamari <bgamari.foss@gmail.com>
To: Ajesh js <coolajeshjs@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Please help me to contribute to btrfs project
Date: Tue, 18 Mar 2014 09:47:23 -0400 [thread overview]
Message-ID: <87wqfrr53o.fsf@gmail.com> (raw)
In-Reply-To: <CA+nQTon3WcD_gdcFyhDwXt=Y7kBu4DZ78YD2=-G+1z8yA2fCQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
Ajesh js <coolajeshjs@gmail.com> writes:
> Hi,
>
> I have used the btrfs filesystem in one of my projects and I have
> added a small feature to it. I feel that the same feature will be
> useful for others too. Hence I would like to contribute the same to
> open source.
>
Excellent!
> If everything works fine and this feature is not already added by
> somebody else, this will be my first contribution to the opensource &
> I am excited to join the huge family of opensource :)
>
> Please help me with a precise steps to do the same.
>
In general the way to contribute is to send a patch for review. You
should have a look at the code style guidelines[1] and patch submission
guidelines[2] in the kernel tree. For nontrivial changes the patch
should be accompanied by a cover letter describing the change and the
motivations for any non-obvious design decisions.
It is possible that your change is acceptable as-is. More likely,
however, is that there will be some discussion and requests for
changes. Eventually the review process will produce a merge-worthy
patch. The first step, however, is sending something concrete for
community review.
Cheers,
- Ben
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/CodingStyle
[2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2014-03-18 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 7:37 Please help me to contribute to btrfs project Ajesh js
2014-03-18 13:47 ` Ben Gamari [this message]
2014-03-19 9:17 ` Ajesh js
2014-03-20 17:52 ` 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=87wqfrr53o.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=coolajeshjs@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