From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Use new tango icon for bluez gnome
Date: Sun, 10 Feb 2008 21:08:11 +0100 [thread overview]
Message-ID: <1202674091.7664.107.camel@violet> (raw)
In-Reply-To: <8a8adccc0802101010y13130615q1c0fec1ff8e84041@mail.gmail.com>
Hi Jaap,
> > I did my own patch to handle the update-icon-cache thing properly in
> > cases of distcheck and the maintainers.
> >
> > For now I also only included the 22x22 icons. Still have to re-think the
> > file structure. Would be nice if we had some nice templates for doing
> > this properly within one directory.
> >
> Here's a template
> Take a look at how vinagre does this
>
> http://svn.gnome.org/viewvc/vinagre/trunk/data/icons/
did it this way. Some nice autoconf/automake macros for it in some
generic way would be nice. Found actually some bugs talking about it,
but nobody did it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-10 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 15:01 [Bluez-devel] [PATCH] Use new tango icon for bluez gnome Jaap A. Haitsma
2008-02-10 16:01 ` Marcel Holtmann
2008-02-10 16:31 ` Jaap A. Haitsma
2008-02-10 16:42 ` Marcel Holtmann
2008-02-10 17:24 ` Jaap A. Haitsma
2008-02-10 17:52 ` Marcel Holtmann
2008-02-10 18:10 ` Jaap A. Haitsma
2008-02-10 20:08 ` Marcel Holtmann [this message]
2008-02-10 18:21 ` Jaap A. Haitsma
2008-02-10 20:09 ` Marcel Holtmann
2008-02-10 21:54 ` Jaap A. Haitsma
2008-02-10 22:12 ` Marcel Holtmann
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=1202674091.7664.107.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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