From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Question Date: Wed, 13 Aug 2008 09:19:53 -0400 Message-ID: <1218633593.15342.350.camel@think.oraclecorp.com> References: <91a37e890808121306g6a288b42n2ee2ecf477699289@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Morey Roof , linux-btrfs@vger.kernel.org To: jeffschroeder@computer.org Return-path: In-Reply-To: List-ID: On Tue, 2008-08-12 at 13:32 -0700, Jeff Schroeder wrote: > On Tue, Aug 12, 2008 at 1:06 PM, Morey Roof 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