From: Chris Mason <chris.mason@oracle.com>
To: jeffschroeder@computer.org
Cc: Morey Roof <moreyroof@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Question
Date: Wed, 13 Aug 2008 09:19:53 -0400 [thread overview]
Message-ID: <1218633593.15342.350.camel@think.oraclecorp.com> (raw)
In-Reply-To: <c24352ca0808121332u682d82a4na91477f77ac9a924@mail.gmail.com>
On Tue, 2008-08-12 at 13:32 -0700, Jeff Schroeder wrote:
> On Tue, Aug 12, 2008 at 1:06 PM, Morey Roof <moreyroof@gmail.com> wrote:
> > I was wondering if someone could give me a few hints. I noticed that
> > all patches have [PATCH] in the subject. Should this always be done?
> > Also, any other general rules to follow that could be passed on would
> > be nice.
>
> Chris feel free to correct me on this, but...
> Since btrfs is Linux kernel code, the same rules apply for btrfs kernel code as
> they do for Linux kernel code. Take a look at Documentation/SubmittingPatches
> in a checkout of the kernel source. It is online here:
> http://users.sosdg.org/~qiyong/lxr/source/Documentation/SubmittingPatches
>
> You can format your patch submission emails correctly with git-send-email(1).
Yes, in general the same rules apply to btrfs as the rest of the kernel.
But, one of my goals it to get new people involved and so I try fixup
imperfect patches as well.
-chris
next prev parent reply other threads:[~2008-08-13 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 20:06 Question Morey Roof
2008-08-12 20:32 ` Question Jeff Schroeder
2008-08-13 13:19 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-20 15:19 question lilofile
2013-10-20 16:53 ` question Hugo Mills
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=1218633593.15342.350.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=jeffschroeder@computer.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=moreyroof@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;
as well as URLs for NNTP newsgroup(s).