Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>,
	Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: SVG version of GDB mascot (archer fish)
Date: Mon, 25 Sep 2017 23:12:00 -0000	[thread overview]
Message-ID: <3105e71c-9eab-fa68-6cb1-63ef9e0cdbb9@redhat.com> (raw)
In-Reply-To: <20170925222843.n74fdmen4fygs4si@adacore.com>

On 09/25/2017 11:28 PM, Joel Brobecker wrote:
>> Since 2001 the GDB project uses the drawing of an archer fish as its
>> logo.  The drawing was made by Jamie Guinan, who scanned it into a JPG
>> file.  That image is currently used on all the GDB web pages.
>>
>> I've created an SVG version of that drawing and used it for my last GNU
>> Tools Cauldron slides.  Here's a slightly improved version.  Would this
>> be of interest?  If so, I might be able to provide a patch for the GDB
>> web site, not sure how to commit it though.

This is awesome!

> 
> I would say so.
> 
> I could help with the import, since I have write access to
> the GDB web pages. It looks like generally supported by most
> web browsers, so if your SVG doesn't use any feature that's
> too fancy, we should be able to just import it, right?
> 
> Should I go ahead?

https://sourceware.org/gdb/mascot/ should be updated
to point at/mention this contribution too.

Is this an Inkspace SVG?  If so, I believe that it's a good
idea to export it as an Optimized SVG for the web.

If already optimized / stripped of custom extensions, it
may be desirable to also provide access to the original file
for future editing and adaptation, if Andreas is willing.

Do we need to say something about copyright/license?

Thanks,
Pedro Alves


  reply	other threads:[~2017-09-25 23:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 17:04 Andreas Arnez
2017-09-25 22:28 ` Joel Brobecker
2017-09-25 23:12   ` Pedro Alves [this message]
2017-09-26 11:36     ` Andreas Arnez
2017-09-26 11:46       ` Pedro Alves
2017-09-26 12:06         ` Andreas Arnez
2017-09-26 13:16           ` Pedro Alves
2017-09-29 12:41       ` Eli Zaretskii
2017-09-29 17:19         ` Andreas Arnez
2017-09-29 18:13           ` Eli Zaretskii
2017-10-04 13:30             ` Andreas Arnez
2017-10-04 14:08         ` Pedro Alves
2017-10-04 14:45           ` Eli Zaretskii
2017-10-04 14:48             ` Pedro Alves
2017-10-04 16:56               ` Eli Zaretskii
2017-10-06  9:17                 ` Andreas Arnez
2017-09-26 11:40   ` Andreas Arnez
2017-09-26 12:40     ` Joel Brobecker

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=3105e71c-9eab-fa68-6cb1-63ef9e0cdbb9@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.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