linux-kernel - Re: [PATCH v2 07/10] trace-cmd: Mov init_common_record_context in parse_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] [day] [month] [year] [list]

Message-ID: <1512127216.4897.200.camel@gmail.com>
Date:   Fri, 01 Dec 2017 13:20:16 +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 07/10] trace-cmd: Mov init_common_record_context in
 parse_record_options

On Thu, 2017-11-30 at 12:07 -0500, Steven Rostedt wrote:
> Same here. It's "Move" not "Mov" ;-)
> 

Yep, that was a desperate attempt to save just one character :-)

I couldn't abbreviate the function names nor skip "in" nor
the "trace-cmd: " prefix.

Only the poor "Move" remained.

I couldn't even add a dot because:
	len("move") == len("mov.")

Sad story.

> I made the modification while pulling in the patch.
> 

Thanks for doing that. "Move" it's by far better!


Vlad