From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Submitting patches
Date: Mon, 26 Feb 2007 15:57:52 -0600 [thread overview]
Message-ID: <45E357E0.50403@freescale.com> (raw)
In-Reply-To: <528646bc0702261250v5845bf33s65a71a9c8321059a@mail.gmail.com>
Grant Likely wrote:
> hehehe, that's a lot of work for a simple thing. Drop the git-commit
> -m flag and use -F instead to add the commit log from a file (or use
> neither and git-commit will bring up an editor).
I haven't tried it, but according to the online help, -F sets the commit
*message*, which is the one-line text that becomes the subject line.
git-commit.txt contains the block of text that appears above the "diff" line.
> You can also use -s
> to add your signoff line too.
I do use -s:
PATCHFILE=`git-format-patch -s $IGNOREEOL HEAD^ `
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-26 21:57 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
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 [this message]
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=45E357E0.50403@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox