From: David Miller <davem@davemloft.net>
To: remi.denis-courmont@nokia.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/8] Phonet: fix NULL-deref in a8059512b120362b15424f152b2548fe8b11bd0c
Date: Tue, 08 Mar 2011 11:29:23 -0800 (PST) [thread overview]
Message-ID: <20110308.112923.39177383.davem@davemloft.net> (raw)
In-Reply-To: <1299592626-18510-1-git-send-email-remi.denis-courmont@nokia.com>
From: Rémi Denis-Courmont <remi.denis-courmont@nokia.com>
Date: Tue, 8 Mar 2011 15:56:59 +0200
> Signed-off-by: Rémi Denis-Courmont <remi.denis-courmont@nokia.com>
You don't even read what I tell you, which makes reviewing your work
insanely frustrating.
I said:
Reference other changes like a man, by mentioned the SHA1 ID and
giving the commit message header line inside of ("") right
afterwards. :-)
I didn't say to put the SHA1 reference in the subject line, it's
so messy there. Put it in the commit message. Do you see other
people putting commit ID references in the commit header line?
Also, I said explicitly to reference the commit like this:
$(SHA1_ID) ("commit message header line")
so in this case it would be:
a8059512b120362b15424f152b2548fe8b11bd0c ("Phonet: implement
per-socket destination/peer address")
because when commits get backported that SHA1_ID might be different
in the tree it gets backported to, so you have to provide that
textual reference to the commit so that in such a case it can still
be matched up.
It also irks me that you persisted to provide the most terse possible
one-line commit message. Have a conversation in your commit message,
this isn't for you it's for other people trying to understand your
work.
The commit message header line just gives a top-level description.
Details like the reasoning, reference to relevant commits, etc.
belong in the commit message contents.
next prev parent reply other threads:[~2011-03-08 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:56 [RFCv3] [PATCH 0/8] net-next: Phonet fixes and cleanup Rémi Denis-Courmont
2011-03-08 13:56 ` [PATCH 1/8] Phonet: fix NULL-deref in a8059512b120362b15424f152b2548fe8b11bd0c Rémi Denis-Courmont
2011-03-08 19:29 ` David Miller [this message]
2011-03-08 20:59 ` Rémi Denis-Courmont
2011-03-08 21:09 ` David Miller
2011-03-08 21:30 ` Rémi Denis-Courmont
2011-03-08 21:34 ` David Miller
2011-03-08 13:57 ` [PATCH 2/8] Phonet: return an error when skb TX fails Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 3/8] Phonet: correct pipe backlog callback return values Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 4/8] Phonet: factor common code to send control messages Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 5/8] Phonet: allocate sock from accept syscall rather than soft IRQ Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 6/8] Phonet: provide pipe socket option to retrieve the pipe identifier Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 7/8] Phonet: support active connection without pipe controller on modem Rémi Denis-Courmont
2011-03-08 13:57 ` [PATCH 8/8] Phonet: kill the ST-Ericsson pipe controller Kconfig Rémi Denis-Courmont
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=20110308.112923.39177383.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=remi.denis-courmont@nokia.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;
as well as URLs for NNTP newsgroup(s).