All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Submitting patches
Date: Mon, 26 Feb 2007 13:29:35 -0600	[thread overview]
Message-ID: <45E3351F.1000809@freescale.com> (raw)
In-Reply-To: <131AF8573CF31945B5B11E4201D3F1E142BB34@mail3.Avidyne.com>

Matt Gessner wrote:
> Hi, 
> 
> The README file doesn't cover how to submit patches for U-Boot using
> git.
> Is it as simple as just pulling the diffs out for each file and
> submitting them?  

Yes.  Use git-format-patch to make the patch, and git-send-email to send it to 
this list.  Make sure you add a changelog to the patch before emailing it.

Also, if the patch is under the purview of one of the CPU family maintainers, 
you should CC: him on it.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-02-26 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 15:51 [U-Boot-Users] Submitting patches Matt Gessner
2007-02-26 19:29 ` Timur Tabi [this message]
2007-02-26 20:06   ` Grant Likely
2007-02-26 20:12     ` Timur Tabi
2007-02-26 20:50       ` Grant Likely
2007-02-26 21:57         ` Timur Tabi
2007-02-26 22:58           ` Grant Likely
2007-02-26 23:04             ` Timur Tabi

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=45E3351F.1000809@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.