From: David Sterba <dsterba@suse.cz>
To: Ajesh js <coolajeshjs@gmail.com>
Cc: Ben Gamari <bgamari.foss@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Please help me to contribute to btrfs project
Date: Thu, 20 Mar 2014 18:52:52 +0100 [thread overview]
Message-ID: <20140320175252.GL29256@twin.jikos.cz> (raw)
In-Reply-To: <CA+nQTom=VFTK61Nkgmwd53hRgXS+kzWixZ725L+ksBcrAqFc9Q@mail.gmail.com>
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:'.
prev parent reply other threads:[~2014-03-20 17:52 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
2014-03-19 9:17 ` Ajesh js
2014-03-20 17:52 ` David Sterba [this message]
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=20140320175252.GL29256@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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