From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] rm_work
Date: Sun, 08 Apr 2007 22:58:09 +0100 [thread overview]
Message-ID: <1176069490.5844.9.camel@localhost.localdomain> (raw)
In-Reply-To: <46191FDD.1000406@dominion.kabel.utwente.nl>
On Sun, 2007-04-08 at 19:01 +0200, Koen Kooi wrote:
> Richard Purdie schreef:
> > As I see it, rm_work is a policy which can be applied by an individual
> > or a distro. I don't think it should be mandatory but if certain distros
> > wish to use it be default, that is up to them and I'm fine with that.
>
> Right, my proposal does that, but skips the need to add it to INHERITS manually. It's a
> small nuance, but not big enough to discuss further :)
Well, your proposed solution requires a magic new variable, using
INHERITS requires no new magic variable and use a standardised method
already used for other such features...
Lets not over complicate things...
Cheers,
Richard
prev parent reply other threads:[~2007-04-08 21:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 10:11 [RFC] rm_work Koen Kooi
2007-04-07 10:34 ` Holger Freyther
2007-04-07 10:41 ` Koen Kooi
2007-04-07 12:25 ` Rod Whitby
2007-04-07 22:03 ` Holger Freyther
2007-04-08 12:07 ` Koen Kooi
2007-04-08 12:21 ` Koen Kooi
2007-04-10 11:31 ` Michael 'Mickey' Lauer
2007-04-08 16:17 ` Richard Purdie
2007-04-11 6:50 ` Marcin Juszkiewicz
2007-04-11 6:55 ` Marcin Juszkiewicz
2007-04-11 8:41 ` Richard Purdie
2007-04-13 19:27 ` Koen Kooi
2007-04-13 22:08 ` Richard Purdie
2007-04-10 10:18 ` Florian Boor
2007-04-08 16:13 ` Richard Purdie
2007-04-08 17:01 ` Koen Kooi
2007-04-08 21:58 ` Richard Purdie [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=1176069490.5844.9.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.