Hi Mark,
On Fri, Jan 31, 2014 at 4:14 PM, Mark Pupilli <[email protected]> wrote:
>
> Nishanth - I would be glad to give whatever information is helpful but being
> a newbie I am not clear about some of the terminology you use e.g. "ensure
> latest linux-next tag and master tags are
> sane and report issues".

Apologies on not being clear:
in the upstream world, two kernels are of significant importance:
1. origin    
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
obviously..
2. linux-next  git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
This one is a daily integration tree of every maintainer tree -
towards a merge window this tends to represent approximately how the
next linux kernel rc1 will look like -> for example next-20140131 is
today's linux-next tag. It is pretty close to what v3.14-rc1 will
eventually look like -> ofcourse things are changing continually in
various maintainer branches, and keeping an eye on daily status is of
interest to folks.

kernel.org tag (or tags in torvald's tree) such as v3.13-rc1, ...
3.13, upcoming 3.14-rc1 etc are the baselines we really want to ensure
working and feature rich. in order to do that, ensuring every such tag
(including rcs) be regularly monitored to ensure things are good and
report issues.

I mean, even if folks dont have a daily cronjob (similar to what I
have for 15 boards), it is still nice to get regular pokes on
linux-omap mailing list asking for status of certain features like how
Robert did for 1GHz. that keeps the rest of us ensuring things work
for everyone else folks start thinking that these platforms are not of
significant interest and tend to feature-rot(die out) over time..

Regards,
Nishanth Menon

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to