linux-kernel - Re: [PATCH v4 0/2] Support kexec/kdump for clang built kernel

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: <CAKwvOdnBKcEFkv2qEWPaFEjPSmR_SXBo2ZGz7ho9pBc88dZJBA@mail.gmail.com>
Date:   Thu, 25 Jul 2019 15:57:34 -0700
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Peter Zijlstra <peterz@...radead.org>,
        clang-built-linux <clang-built-linux@...glegroups.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: [PATCH v4 0/2] Support kexec/kdump for clang built kernel

On Thu, Jul 25, 2019 at 3:51 PM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Thu, 25 Jul 2019, Nick Desaulniers wrote:
>
> I'm really impressed how you manage to make the cover letter (0/N) a reply
> to 1/N instead of 1..N/N being a reply to 0/N.
>
>   In-Reply-To: <20190725200625.174838-1-ndesaulniers@...gle.com>
>   Message-Id: <20190725200625.174838-3-ndesaulniers@...gle.com>
>
> Is that a new git feature to be $corp top-posting compliant?

It appears to be a hidden bonus feature of:
$ git-send-email purgatory/v4-000*

> > V4 of: https://lkml.org/lkml/2019/7/23/864
>
> Please don't use lkml.org references. I know it's popular but equally
> unreliable at times.

Oh?

>
> The long term reliable reference is message id based, i.e.:
>
>  lkml.kernel.org/r/$MSGID
>
> or
>
>  lore.kernel.org/lkml/$MSGID
>
> even if the base URLs would cease to exist, the message id will give you a
> trivial way to find the relevant thread, but if '2019/7/23/864' stops to
> work, good luck in finding the original post. I wasted hours on that just
> because a subject line changed enough to confuse the big internet stalking
> machines.

Thanks for the tips; I'll try to use lore.kernel.org going forward.

-- 
Thanks,
~Nick Desaulniers