On 15 November 2012 11:37, Jon Medhurst (Tixy) <t...@linaro.org> wrote:
> On Thu, 2012-11-15 at 09:20 +0530, Tushar Behera wrote:
>> On 11/14/2012 07:41 PM, Ryan Harkin wrote:
>> > On 14 November 2012 11:38, Jon Medhurst (Tixy) <t...@linaro.org> wrote:
> [...]
>> >> Now that the LT branches included in linux-linaro (ll) are based on
>> >> llct, then they could modify the board configs in llct if required for
>> >> the work in their topics. So at the moment, I can't think of a good
>> >> reason not to pub all the board configs into llct. Can anyone else?
>> >>
>> >> I don't know if we need the board configs to be sourced from a single
>> >> repo, or allow board configs to be included in llct from LT trees. One
>> >> central repo means that people know where to go
>> >
>> > This seems like the easiest option to me.  Let's do it this way unless
>> > someone gives a valid objection.
>> >
>> >> (Unless we had
>> >> an official maintainer to manage all commits to the tree.)
>> >
>> > I assume this would have to be Andrey.  Andrey, are you OK with that?
>> > Or does someone else need to do it?
>> >
>> > Each LT that is using LLCT would have to send a patch to get their
>> > config updated.  So long as this happens in a timely manner, LTs
>> > should be able to live with that process.
>> >
>>
>> I suppose we are talking about the basic board config here. That should
>> be ok. The new board enablement config fragments should always go in
>> with the respective topic branches.
>
> I agree.

OK, can we do it then?  We're freezing for release today, but it's not
a big change, so we can get it in, right?

At some point in the past, Andrey asked:
> My question is if this topic branch would be kernel/configs.git,

Sounds perfect


>  config-boards-tracking branch or something else?

I don't have an opinion.  We'll probably have to live with it for a
long time, but as long as it looks sensible, I'm sure people will be
ok...

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to