From: Prarit Bhargava <prarit@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>,
Daniel Baluta <daniel.baluta@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Update git commit message
Date: Mon, 12 Jan 2015 08:20:42 -0500 [thread overview]
Message-ID: <54B3CA2A.2030004@redhat.com> (raw)
In-Reply-To: <1420840730.32628.13.camel@perches.com>
On 01/09/2015 04:58 PM, Joe Perches wrote:
> The git commit message can be confusing,
>
> Try to clarify the message a bit to reduce
> the confusion when emitted.
>
> Show the correct form using
> Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")'
> and if the git commit sha1 is unique, show
> the right sha1 to use with the actual title
>
> Signed-off-by: Joe Perches <joe@perches.com>
> Original-patch-by: Prarit Bhargava <prarit@redhat.com>
> ---
Acked-by: Prarit Bhargava <prarit@redhat.com>
P.
prev parent reply other threads:[~2015-01-12 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 21:58 Joe Perches
2015-01-10 20:08 ` Chris Rorvick
2015-01-12 13:20 ` Prarit Bhargava [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=54B3CA2A.2030004@redhat.com \
--to=prarit@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=daniel.baluta@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome