lkml.org 
[lkml]   [2018]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] checkpatch: Add a --strict test for structs with bool member definitions
Date
Andrea Parri <andrea.parri@amarulasolutions.com> writes:

> On Thu, Apr 12, 2018 at 09:47:19AM +0200, Ingo Molnar wrote:
>>
>> * Peter Zijlstra <peterz@infradead.org> wrote:
>>
>> > I still have room in my /dev/null mailbox for pure checkpatch patches.
>> >
>> > > (ooh, https://lkml.org/lkml/2017/11/21/384 is working this morning)
>> >
>> > Yes, we really should not use lkml.org for references. Sadly google
>> > displays it very prominently when you search for something.
>>
>> lkml.org is nice in emails that have a short expected life time and relevance -
>> but it probably shouldn't be used for permanent references such as kernel
>> messages, code comments and Git log entries.
>
> Is there a better or recommended way to reference posts on LKML in commit
> messages? (I do like the idea of linking to previous discussions, results,
> ...)

I like lkml.kernel.org, for example a link to your message would be:

https://lkml.kernel.org/r/20180412093521.GA6427@andrea

BTW, I think it would be a good idea to add a hostname to your
Message-Id.

--
Kalle Valo

\
 
 \ /
  Last update: 2018-04-12 13:53    [W:0.071 / U:0.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site