From: Jon Loeliger <jdl@jdl.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 10/10 v2] Document I2C_MPC option for 86xx too.
Date: Fri, 09 Jun 2006 08:50:34 -0500 [thread overview]
Message-ID: <E1FohNi-0003S9-5R@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 09 Jun 2006 09:37:37 +0200." <20060609093737.f66d5a41.khali@linux-fr.org>
So, like, the other day Jean Delvare mumbled:
> Hi Jon,
>
> Please add a paragraph explaining what the patch does. It will be used
> as the git commit message.
Hi Jean,
There is a one-line commit message that will come from
the Subject: line. If I add a paragraph, it will be
"Document I2C_MPC option for 86xx too."
which will end up as a duplicate line in the commit message.
Thanks,
jdl
prev parent reply other threads:[~2006-06-09 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 22:04 [PATCH 10/10 v2] Document I2C_MPC option for 86xx too Jon Loeliger
2006-06-09 7:37 ` Jean Delvare
2006-06-09 13:50 ` Jon Loeliger [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=E1FohNi-0003S9-5R@jdl.com \
--to=jdl@jdl.com \
--cc=khali@linux-fr.org \
--cc=linuxppc-dev@ozlabs.org \
/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.