From: Amit Kucheria <amit.kucheria@verdurent.com>
To: Peter Barada <peterb@logicpd.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Question regarding how to submit patches
Date: Tue, 17 Feb 2009 02:43:27 +0200 [thread overview]
Message-ID: <20090217004327.GA14031@everest.verdurent.com> (raw)
In-Reply-To: <1234799464.3238.460.camel@blackhole>
On Mon, Feb 16, 2009 at 10:51:03AM -0500, Peter Barada wrote:
> Does anyone have a pointer on how to prepare patches for inclusion into
> the linx-omap tree(s)? I'm looking for something that demonstrates it
> as I'm quite unfamiliar with git...
The kernel source has a file Documentation/SubmittingPatches that outlines the basic steps in getting your changes upstream. Kernelnewbies[1] also has a good list of dos and don'ts.
You don't _have_ to use git to submit patches, unified diffs are fine.
Regards,
Amit
[1] http://kernelnewbies.org/UpstreamMerge
--
-------------------------------------------------------------------------
Amit Kucheria amit _dot_ kucheria@<NOSPAM>verdurent.com
Kernel Developer, Verdurent
--------------------------------------------------------------------------
prev parent reply other threads:[~2009-02-17 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 15:51 Question regarding how to submit patches Peter Barada
2009-02-17 0:43 ` Amit Kucheria [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=20090217004327.GA14031@everest.verdurent.com \
--to=amit.kucheria@verdurent.com \
--cc=linux-omap@vger.kernel.org \
--cc=peterb@logicpd.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