From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC/PATCH] Add support for XFCE 4.6.1.
Date: Sun, 25 Oct 2009 14:29:33 +0100 [thread overview]
Message-ID: <hc1jrt$ki8$1@ger.gmane.org> (raw)
In-Reply-To: <44440.3488342234$1256472302@news.gmane.org>
On 25-10-09 13:02, John Willis wrote:
> For now it adds an xfce46.bbclass to support the builds and lives alongside
> of XFCE 4.4 but in fairness I would like to propose dropping XFCE 4.4.* from
> dev (and leaving it in stable/2009 for now).
What would be the big advantage of deleting them? I'm generally not a
fan of deleting recipes "because we can". OE has lots of users that
don't read this mailinglist (which they should...) and generally start
bitching (but not to oe mailinglists, as they should) when we drop
stuff. That's of course largely their own fault for trying to live in
their own insulated bubble, but it would be nice if OE can make their
lives easier.
You're point that stable/2009 would still have them is a valid point :)
regards,
Koen
next parent reply other threads:[~2009-10-25 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44440.3488342234$1256472302@news.gmane.org>
2009-10-25 13:29 ` Koen Kooi [this message]
2009-10-25 12:02 [RFC/PATCH] Add support for XFCE 4.6.1 John Willis
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='hc1jrt$ki8$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.