linux-kernel - Re: [PATCH v6 18/23] docs: add Rust documentation

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: <CANiq72mna9MKSgJYs19k=ieYu4v4TuemLdp1wkyhr9hqJ-tuAQ@mail.gmail.com>
Date:   Tue, 10 May 2022 13:57:40 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Akira Yokosawa <akiyks@...il.com>, Miguel Ojeda <ojeda@...nel.org>,
        Alex Gaynor <alex.gaynor@...il.com>,
        Adam Bratschi-Kaye <ark.email@...il.com>,
        Boris-Chengbiao Zhou <bobo1239@....de>,
        Wu XiangCheng <bobwxc@...il.cn>, Daniel Xu <dxu@...uu.xyz>,
        Gary Guo <gary@...yguo.net>,
        Greg KH <gregkh@...uxfoundation.org>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Yuki Okushi <jtitor@...6.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Julian Merkle <me@...erkle.de>, Finn Behrens <me@...enk.de>,
        Michal Marek <michal.lkml@...kovi.net>,
        Michael Ellerman <mpe@...erman.id.au>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        rust-for-linux <rust-for-linux@...r.kernel.org>,
        Sven Van Asbroeck <thesven73@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Wedson Almeida Filho <wedsonaf@...gle.com>,
        Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH v6 18/23] docs: add Rust documentation

On Tue, May 10, 2022 at 12:37 AM Jonathan Corbet <corbet@....net> wrote:
>
> Yeah, but the issues are all with me :)  Please accept my apologies for
> letting it slip through the cracks.

No apologies needed! It is not an important patch -- I just thought it
would be better to have the "base logo" merged before the "derived
one".

> Looking at it now, though, I hesitate to add the logo (and another
> COPYING file) in the top-level Documentation directory - I'd really
> rather people not have to pick through a bunch of unrelated stuff to
> find the actual docs they want.  I'd recommend we make a
> Documentation/images (or .../assets or whatever) and put things like
> logos there.

Yeah, makes sense to avoid dumping things in the top-level directory.

> Disagree?  If not, could I get a version of the patch that does that?  I
> promise not to set on it for three months this time...

+1, I will send it.

Thanks Jon!

Cheers,
Miguel