From: Jason Gunthorpe <jgg@ziepe.ca>
To: Doug Ledford <dledford@redhat.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] siw: Fix potential NULL pointer in siw_connect().
Date: Wed, 21 Aug 2019 11:12:25 -0300 [thread overview]
Message-ID: <20190821141225.GB8653@ziepe.ca> (raw)
In-Reply-To: <adc716f5d2105a3cc7978873cd0f14503ae323d8.camel@redhat.com>
On Wed, Aug 21, 2019 at 09:39:50AM -0400, Doug Ledford wrote:
> On Wed, 2019-08-21 at 15:56 +0300, Dan Carpenter wrote:
> > On Tue, Aug 20, 2019 at 12:05:33PM -0400, Doug Ledford wrote:
> > > Please take a look (I pushed it out to my wip/dl-for-rc branch) so
> > > you
> > > can see what I mean about how to make both a simple subject line and
> > > a
> > > decent commit message. Also, no final punctuation on the subject
> > > line,
> > > and try to keep the subject length <= 50 chars total. If you have
> > > to go
> > > over to have a decent subject, then so be it, but we strive for that
> > > 50
> > > char limit to make a subject stay on one line when displayed using
> > > git
> > > log --oneline.
> >
> > 50 is really small.
>
> 50 is the vim syntax highlighting suggested limit. You can go over,
> which is why I indicated it was a soft limit, but there you are. It
> leaves room for the displayed hash length to grow as well.
I use 75 for all text in the commit message, as per
Documentation/process/submitting-patches.rst
People using 'git log --oneline' should have terminals wider than 80
:)
The bigger question is if the first character after the subject tag
should be uppper case or lower case <hum>
Jason
next prev parent reply other threads:[~2019-08-21 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 14:02 [PATCH] siw: Fix potential NULL pointer in siw_connect() Bernard Metzler
2019-08-20 16:05 ` Doug Ledford
2019-08-21 12:56 ` Dan Carpenter
2019-08-21 13:39 ` Doug Ledford
2019-08-21 14:12 ` Jason Gunthorpe [this message]
2019-08-21 16:30 ` Leon Romanovsky
2019-08-22 6:35 ` Gal Pressman
2019-08-22 7:10 ` Dan Carpenter
2019-08-22 12:02 ` Jason Gunthorpe
2019-08-22 15:02 ` Doug Ledford
2019-08-20 16:11 ` Bernard Metzler
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=20190821141225.GB8653@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bmt@zurich.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).