public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
* Please help me to contribute to btrfs project
@ 2014-03-18  7:37 Ajesh js
  2014-03-18 13:47 ` Ben Gamari
  0 siblings, 1 reply; 4+ messages in thread
From: Ajesh js @ 2014-03-18  7:37 UTC (permalink / raw)
  To: linux-btrfs

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.

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.

Thank you,
Ajesh

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Please help me to contribute to btrfs project
  2014-03-18  7:37 Please help me to contribute to btrfs project Ajesh js
@ 2014-03-18 13:47 ` Ben Gamari
  2014-03-19  9:17   ` Ajesh js
  0 siblings, 1 reply; 4+ messages in thread
From: Ben Gamari @ 2014-03-18 13:47 UTC (permalink / raw)
  To: Ajesh js, linux-btrfs

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Please help me to contribute to btrfs project
  2014-03-18 13:47 ` Ben Gamari
@ 2014-03-19  9:17   ` Ajesh js
  2014-03-20 17:52     ` David Sterba
  0 siblings, 1 reply; 4+ messages in thread
From: Ajesh js @ 2014-03-19  9:17 UTC (permalink / raw)
  To: Ben Gamari; +Cc: linux-btrfs

Thank you very much Ben :)

I did go though the links send by you & got the complete details for
sending the kernel component.

Also my change has a patch in btrfs-tools. It will be nice if you can
share the process for submitting that patch also.

Regards,
Ajesh

On Tue, Mar 18, 2014 at 7:17 PM, Ben Gamari <bgamari.foss@gmail.com> wrote:
> 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
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Please help me to contribute to btrfs project
  2014-03-19  9:17   ` Ajesh js
@ 2014-03-20 17:52     ` David Sterba
  0 siblings, 0 replies; 4+ messages in thread
From: David Sterba @ 2014-03-20 17:52 UTC (permalink / raw)
  To: Ajesh js; +Cc: Ben Gamari, linux-btrfs

On Wed, Mar 19, 2014 at 02:47:50PM +0530, Ajesh js wrote:
> I did go though the links send by you & got the complete details for
> sending the kernel component.
> 
> Also my change has a patch in btrfs-tools. It will be nice if you can
> share the process for submitting that patch also.

The patch submission process and coding style is the same for userspace
tools. The common practice is to prefix the subject of patch that
modifies userspace tools with 'btrfs-progs:'.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-03-20 17:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-18  7:37 Please help me to contribute to btrfs project Ajesh js
2014-03-18 13:47 ` Ben Gamari
2014-03-19  9:17   ` Ajesh js
2014-03-20 17:52     ` David Sterba

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox