[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8735hicoy7.fsf@meer.lwn.net>
Date: Mon, 09 May 2022 16:37:36 -0600
From: Jonathan Corbet <corbet@....net>
To: Akira Yokosawa <akiyks@...il.com>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: 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
Akira Yokosawa <akiyks@...il.com> writes:
> [+To: Jon]
>
> On Mon, 9 May 2022 12:41:28 +0200,
> Miguel Ojeda wrote:
>> Hi Akira,
>>
>> On Mon, May 9, 2022 at 6:02 AM Akira Yokosawa <akiyks@...il.com> wrote:
>>>
>>> I think you agreed splitting SVG part into its own patch with
>>> a proper copying info, etc. Let me see... So, here is the link:
>>
>> Yes, sorry, will do (in fact, it should have been there in v5 too).
>>
>> By the way, the Linux SVG logo (used to make the one here) is pending
>> in the linux-doc ML.
>
> So you mean the following post:
>
> https://lore.kernel.org/lkml/20220207014418.GA28724@kernel.org/
>
> I'm not sure why Jon has not responded.
>
> Jon, was there any issue on this patch?
Yeah, but the issues are all with me :) Please accept my apologies for
letting it slip through the cracks.
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.
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...
Thanks,
jon
Powered by blists - more mailing lists