On 19/07/12 16:23, Martin Jansa wrote:
On Thu, Jul 19, 2012 at 03:44:50PM +0100, Jack Mitchell wrote:
On 18/07/12 11:06, Richard Purdie wrote:
snip
So I am going to:
a) Try and flush through as many pending patches as I can.
b) Check in a warning into bitbake master and increase its version
c
On Thu, Jul 19, 2012 at 03:44:50PM +0100, Jack Mitchell wrote:
> On 18/07/12 11:06, Richard Purdie wrote:
> > snip
> >
> > So I am going to:
> >
> > a) Try and flush through as many pending patches as I can.
> > b) Check in a warning into bitbake master and increase its version
> > c) Require that
On 18/07/12 11:06, Richard Purdie wrote:
snip
So I am going to:
a) Try and flush through as many pending patches as I can.
b) Check in a warning into bitbake master and increase its version
c) Require that version in OE-Core
d) Commit a significant set of whitespace changes to OE-Core, resolvin
On Wed, 2012-07-18 at 11:17 +0100, Burton, Ross wrote:
> On 18 July 2012 11:06, Richard Purdie
> wrote:
> > I put a proposal to the TSC, that we have bitbake warn/error whenever it
> > finds tab characters in any python function. The advantage of this is
> > that we give the user a clear definitiv
On 18 July 2012 11:06, Richard Purdie
wrote:
> I put a proposal to the TSC, that we have bitbake warn/error whenever it
> finds tab characters in any python function. The advantage of this is
> that we give the user a clear definitive error. The downside is that
> we'll have to go through all the
It's become clear we have a horrible mixture of whitespace (tabs and
space) in python functions. At first glance this sounds trivial but
there is a serious problem if pieces of code get mixed together with
different whitespace since they may or may not work as intended.
The documented standard for
