linux-kernel - Re: [PATCH v2 06/10] trace-cmd: Extr. profile-specific code from record

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1512126649.4897.192.camel@gmail.com>
Date:   Fri, 01 Dec 2017 13:10:49 +0200
From:   Vladislav Valtchev <vladislav.valtchev@...il.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     linux-kernel@...r.kernel.org, y.karadz@...il.com
Subject: Re: [PATCH v2 06/10] trace-cmd: Extr. profile-specific code from
 record_trace

On Thu, 2017-11-30 at 12:05 -0500, Steven Rostedt wrote:
> I modified the subject to:
> 
>  trace-cmd: Extract profile-specific code from record_trace
> 
> Let's not abbreviate in the subject if we don't need to. It makes it
> harder to read.
> 

I'm totally fine with not abbreviating so much the subject!

I did that because of posts like this:

https://stackoverflow.com/questions/2290016/git-commit-messages-50-72-formatting

and because vim shows in yellow the first 50 characters of the summary, to help
people following that limitation. In order words, I've understood that I shall
try to fit in 50 chars and never exceed 72 chars.

That lead me to desperate attempts to save characters, like in patch 7 where
I tried to abbreviate "move" with "mov", but I couldn't add a dot for obvious
reasons. [Until now, I was used to make the summary fit in 80 characters.]

What is the convention for trace-cmd?
In particular, what's the hard-limit I shall never exceed ?

Vlad