qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH] Add a favicon.ico file
Date: Wed, 26 Jul 2017 15:32:16 +0200	[thread overview]
Message-ID: <4435a881-308c-6f7b-8e01-ef8f4512221c@redhat.com> (raw)
In-Reply-To: <1501075650-6971-1-git-send-email-thuth@redhat.com>

On 26/07/2017 15:27, Thomas Huth wrote:
> Most browsers try to download a /favicon.ico file from the web servers
> which is then e.g. used in the browser tabs or bookmark lists. So let's
> add such a file for the QEMU website, too. The .ico has been created
> resizing the logo from http://wiki.qemu.org/Logo to 16x16 pixels.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  If I've got the Jekyll magic right, it should be enough to create this
>  file in the top of the repository, right? Or do we need to mark this
>  in one of the configuration files, too?

The icon appears in the built site, but I don't see it if I test this
locally with "jekyll serve".

It doesn't hurt really, so go ahead and push it. :)

Paolo

>  favicon.ico | Bin 0 -> 1150 bytes
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  create mode 100644 favicon.ico
> 
> diff --git a/favicon.ico b/favicon.ico
> new file mode 100644
> index 0000000000000000000000000000000000000000..f22440604f92468c7102b1293bcc59426f0e5bbd
> GIT binary patch
> literal 1150
> zcmaizQAkr^6vxk&tGVdTETpGpNakuH(R%P9qV-Ul4}yd~lml1Jgz6y}S|r4v2VL}1
> z53Nz8R?tIWv_~sfFJab05QA8yk=07KW!v2D?(WzBY`Y;+bjI(Vd(U_O=bZ05cSJh;
> zYHA4AdOBG}R7XTj03k%maX2EZMK_cwJ^%f}@_uj+JO`8DCg=w1K^VLQ(_lZ)Oplv0
> z-~)(*A7FuMn^W+K3iI%bfY;sv17Krq5PSuic99yp)3micjTq-(l7Mq@jv=7g0B%-l
> z6I8u9MaRCVWUTvzwWSI_;W-EEdjVTLm;+i}<kzL>(4zu%yecBj^%*UXwx9QiN#Fwb
> z26#`LH$}V8=g2Dr?Y$)9Ia?tE&pEgU-opa$fG6NPU~Q6i^ej_vQIzy`t*p<1Ww2V$
> z^+rJqaIOSx*_ZyK^{PUusg)&3Vsa*vDXZ7(SJr3!V=xO!eVg{2E%%Myb-jw%xvRNo
> zv)L4o2RW<NnlTs*ynlY5d*<F>fF$BejYn=2N`3R*!S>Ek^{~^WIGs+}<#OfP+S;;q
> zyPapj{qlK_gAtHwXlTeB?7O9`)bsr&?`QQu-)*JKJCt{H4d&aAo?6B}xOYBtFKA&s
> z@@5A7R|~qna_w>+RaCj>g`w+>Sl2ltHg<$n=ZVX*(P(5n&yT-#wrduPB{McQrZoBD
> zs@8+vs|a0-Pe`6Q;U1Y*#>emE1Azd~lWU)5Va2N9C;fiE9DFcST-#rnANrS$e-f?d
> z-l<QgB85mKB0C%op8a*8t7tV>Z8n=j!C+AK-Ca<7f(a3L7+0UYo-M{=v0^kDRXiRK
> zYX<@UU;bq+Znyh>C=`l^!{OY-#6)&@c=#jE=L!VdR*QI;Q{W=HVg6^@dsAz0=w_nd
> DdRjod
> 
> literal 0
> HcmV?d00001
> 

  reply	other threads:[~2017-07-26 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 13:27 [Qemu-devel] [qemu-web PATCH] Add a favicon.ico file Thomas Huth
2017-07-26 13:32 ` Paolo Bonzini [this message]
2017-07-26 14:02 ` Daniel P. Berrange
2017-07-26 14:17   ` Thomas Huth
2017-07-26 14:38     ` Paolo Bonzini
2017-07-26 14:47       ` Thomas Huth
2017-07-26 14:54         ` Paolo Bonzini
2017-07-26 16:43           ` Jeff Cody
2017-07-27  9:24           ` Thomas Huth
2017-07-27  9:55             ` Daniel P. Berrange
2017-07-27 12:15             ` Paolo Bonzini
2017-07-26 14:46     ` Daniel P. Berrange

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=4435a881-308c-6f7b-8e01-ef8f4512221c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jcody@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).