All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: {TSC] request to discuss items.
Date: Mon, 01 Mar 2010 16:01:15 -0500	[thread overview]
Message-ID: <4B8C2B1B.40604@balister.org> (raw)
In-Reply-To: <ac9c93b11003011133wa0f4e3bqe7af69ead4d7eec6@mail.gmail.com>

On 03/01/2010 02:33 PM, Frans Meulenbroeks wrote:
> As we have (as far as I know) no procedure to table issues for the
> TSC, I'm proposing two issues for the TSC:

 > 1) the location of distro specific files

This is a little premature ... There is a good discussion going on about 
this at the moment. It takes time for the community to draw a conclusion 
on matters like this.

> 2) how to handle legacy recipes that are not used by any known distro

I'd note that this issue has come up before, and the consensus is no 
major shuffling of recipes for aesthetic reasons. I don't see any 
changes that would change the conclusion this time. I believe all of the 
TSC members are already involved in the on list discussion.

Philip

>
> Both have been discussed on this list, and several options have been coined
> E.g. for 1) dedicated directories, overlays or retain the current solution
> And for 2) an overlay, and "obsolete" directory, retain the current
> solution and remove the recipes.
>
> May I ask the TSC to provide a verdict on these.
>
> Thanks alot,
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



  reply	other threads:[~2010-03-01 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 19:33 {TSC] request to discuss items Frans Meulenbroeks
2010-03-01 21:01 ` Philip Balister [this message]
2010-03-01 21:37   ` Frans Meulenbroeks

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=4B8C2B1B.40604@balister.org \
    --to=philip@balister.org \
    --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.