From: Steffen Sledz <sledz@dresearch-fe.de>
To: Richard Leitner <richard.leitner@skidata.com>,
openembedded-devel@lists.openembedded.org,
openembedded-core <openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Martin Jansa <martin.jansa@gmail.com>,
Koen Kooi <koen@dominion.thruhere.net>
Cc: Benjamin Reikowski <reikowski@dresearch-fe.de>
Subject: Re: [oe] cups-filters
Date: Thu, 22 Oct 2015 11:01:36 +0200 [thread overview]
Message-ID: <5628A5F0.2060009@dresearch-fe.de> (raw)
In-Reply-To: <5628A439.1030200@skidata.com>
On 22.10.2015 10:54, Richard Leitner wrote:
> On 10/22/2015 10:52 AM, Steffen Sledz wrote:
>> On 22.10.2015 09:50, Richard Leitner wrote:
>>> On 10/21/2015 04:01 PM, Steffen Sledz wrote:
>>>> Does anybody know about a recipe providing cups-filters?
>>>>
>>>> http://layers.openembedded.org was not really helpful here.
>>>
>>> I have one which works for my purposes but it is not really tested...
>>> It is based on something I found somewhere on the web (I don't remember
>>> the source).
>>
>> Any plans to make this part of an official layer?
>>
> Currently I have no time for creating and testing a clean patch for it.
> But if anybody has time and motivation, feel free to do it ;-)
I could try to prepare one.
@layer-maintainers: What would be the right layer for this? openembedded-core or meta-oe?
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
prev parent reply other threads:[~2015-10-22 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 14:01 cups-filters Steffen Sledz
[not found] ` <5628952C.8080706@skidata.com>
2015-10-22 8:52 ` [oe] cups-filters Steffen Sledz
[not found] ` <5628A439.1030200@skidata.com>
2015-10-22 9:01 ` Steffen Sledz [this message]
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=5628A5F0.2060009@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=reikowski@dresearch-fe.de \
--cc=richard.leitner@skidata.com \
--cc=richard.purdie@linuxfoundation.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