rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Miguel Ojeda <ojeda@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Adam Bratschi-Kaye <ark.email@gmail.com>,
	Boris-Chengbiao Zhou <bobo1239@web.de>,
	Wu XiangCheng <bobwxc@email.cn>, Daniel Xu <dxu@dxuuu.xyz>,
	Gary Guo <gary@garyguo.net>, Greg KH <gregkh@linuxfoundation.org>,
	Yuki Okushi <jtitor@2k36.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Finn Behrens <me@kloenk.de>,
	Michal Marek <michal.lkml@markovi.net>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nick Desaulniers <ndesaulniers@google.com>,
	rust-for-linux <rust-for-linux@vger.kernel.org>,
	Sven Van Asbroeck <thesven73@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Wedson Almeida Filho <wedsonaf@google.com>,
	Wei Liu <wei.liu@kernel.org>
Subject: Re: [PATCH v4 15/20] docs: add Rust documentation
Date: Thu, 17 Mar 2022 23:50:42 +0900	[thread overview]
Message-ID: <61547556-790f-f74f-ca2e-b2fde714a7fa@gmail.com> (raw)
In-Reply-To: <CANiq72mQffofeW4C=AWF4CHu=WpgpwB4hAv_q9QiTX_+U38qGg@mail.gmail.com>

Hi Miguel,

On Thu, 17 Mar 2022 09:19:37 +0100,
Miguel Ojeda wrote:
> Hi Akira,
> 
> On Mon, Feb 14, 2022 at 11:47 AM Akira Yokosawa <akiyks@gmail.com> wrote:
>>
>>> diff --git a/Documentation/rust/logo.svg b/Documentation/rust/logo.svg
>>> new file mode 100644
>>> index 000000000000..65be792a5abe
>>> --- /dev/null
>>
>> How about adding a suitable license identifier in a comment?
> 
> For the next round, I did not apply this suggestion, because it is
> unclear which license identifier to use: it would be probably be the
> same as the `COPYING-logo` one (which would be used also for the Tux
> SVG, if it gets merged -- it was sent a while ago).

I see.

As I see v2 15/20, the SVG figure is among other documentation updates.
IIUC, this figure/logo was in PNG at first, but Jon suggested vector graphics.
If this is the case, it deserves an individual patch with a changelog
explaining why it is in SVG, where the Tux figure came from, what was the
original PNG logo, who contributed the SVG conversion, etc.

I understand you did all the SVG work, didn't you?
I don't think those many Co-developed-by tags apply to this figure.

I'm saying this because this figure/logo can be reused in other open-
source projects on its own.  It would be worth clarifying its origin 
in the Git history as well as in COPYING-logo.

        Thanks, Akira

> 
> Cheers,
> Miguel

  reply	other threads:[~2022-03-17 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220212130410.6901-16-ojeda@kernel.org>
2022-02-14 10:47 ` [PATCH v4 15/20] docs: add Rust documentation Akira Yokosawa
2022-02-14 12:44   ` Miguel Ojeda
2022-02-16 13:37   ` Akira Yokosawa
2022-02-16 14:02     ` Miguel Ojeda
2022-03-17  8:19   ` Miguel Ojeda
2022-03-17 14:50     ` Akira Yokosawa [this message]
2022-03-18 13:12       ` Miguel Ojeda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61547556-790f-f74f-ca2e-b2fde714a7fa@gmail.com \
    --to=akiyks@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=ark.email@gmail.com \
    --cc=bobo1239@web.de \
    --cc=bobwxc@email.cn \
    --cc=corbet@lwn.net \
    --cc=dxu@dxuuu.xyz \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jtitor@2k36.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=me@kloenk.de \
    --cc=michal.lkml@markovi.net \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=thesven73@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wedsonaf@google.com \
    --cc=wei.liu@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).