From: Chris Larson <clarson@kergoth.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path
Date: Wed, 11 Jul 2012 12:01:45 -0700 [thread overview]
Message-ID: <CABcZANmXGq8kccKxaqtwG7ekBqSsEzCwmwjTHSbXo9c5VsS-Pg@mail.gmail.com> (raw)
In-Reply-To: <20120711135455.72b90a06@wrlaptop>
On Wed, Jul 11, 2012 at 11:54 AM, Peter Seebach
<peter.seebach@windriver.com> wrote:
> Okay, crazy thought. Imagine that we were to make a modified parser,
> with the following behavior:
>
> Whenever reading a python function, count the indentation of the first
> line (N), then replace every N spaces of indentation with 4 spaces.
>
> If this worked, it would make it possible to start fixing stuff.
That's one possibility. The other would be to treat _append/_prepended
functions as independent entities. Rather than concatenating
functions, it'd add them to the prefuncs/postfuncs or equivalent.
Without concatenation, there'd be no issues with mismatches.
--
Christopher Larson
next prev parent reply other threads:[~2012-07-11 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:00 [PATCH 0/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
2012-07-11 16:00 ` [PATCH 1/1] " Peter Seebach
2012-07-11 16:12 ` Richard Purdie
2012-07-11 16:33 ` Peter Seebach
2012-07-11 17:36 ` Richard Purdie
2012-07-11 17:56 ` Ross Burton
2012-07-11 18:54 ` Peter Seebach
2012-07-11 19:01 ` Chris Larson [this message]
2012-07-11 19:54 ` Burton, Ross
2012-07-11 20:20 ` Richard Purdie
2012-07-11 20:31 [PATCH 0/1] package.bbclass: Allow overriding of debugedit base path Peter Seebach
2012-07-11 20:31 ` [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
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=CABcZANmXGq8kccKxaqtwG7ekBqSsEzCwmwjTHSbXo9c5VsS-Pg@mail.gmail.com \
--to=clarson@kergoth.com \
--cc=openembedded-core@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.