From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Adrian Bunk <bunk@stusta.de>, Armin Kuster <akuster808@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [Warrior][ 15/19] texinfo-dummy-native: A little clean up of template.py
Date: Mon, 24 Jun 2019 12:42:17 +0000 [thread overview]
Message-ID: <5ddcbbe68f00435fa57cf14b59e4863d@XBOX04.axis.com> (raw)
In-Reply-To: <cdffa8e2d2d7ed81450272040d6e18eceb447f08.camel@linuxfoundation.org>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org <openembedded-
> core-bounces@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 24 juni 2019 12:23
> To: Adrian Bunk <bunk@stusta.de>; Armin Kuster <akuster808@gmail.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [Warrior][ 15/19] texinfo-dummy-native: A little
> clean up of template.py
>
> On Mon, 2019-06-24 at 10:38 +0300, Adrian Bunk wrote:
> > On Sun, Jun 23, 2019 at 08:54:14PM -0700, Armin Kuster wrote:
> > > From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > >
> > > This is mainly whitespace clean up, plus using the with statement
> > > when
> > > writing files.
> > > ...
> >
> > This patch and the next two look more like cleanup patches to me,
> > not changes that should go into a stable series.
Yes, this patch is pure cleanup, however, it is preparation for the next
patch, which is not cleanup. The next patch fixes a problem with one of
our recipes that uses the texinfo bbclass if the build path happens to
contain the letter "E"...
> FWIW the package.bbclass change is being requested to allow people to
> stop patching the class...
Exactly.
> Cheers,
>
> Richard
//Peter
next prev parent reply other threads:[~2019-06-24 12:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 3:53 [Warrior][ 00/19] patch review Armin Kuster
2019-06-24 3:54 ` [Warrior][ 01/19] util-linux: Stop udevd to run ptests Armin Kuster
2019-06-24 3:54 ` [Warrior][ 02/19] linux-yocto: Add scsi_debug module when ptest is in DISTRO_FEATURES Armin Kuster
2019-06-24 10:50 ` Martin Jansa
2019-06-24 3:54 ` [Warrior][ 03/19] selftest/devtool: fix URI to MarkupSafe package Armin Kuster
2019-06-24 3:54 ` [Warrior][ 04/19] diffutils/run-ptest: support to run at arbitrary path Armin Kuster
2019-06-24 3:54 ` [Warrior][ 05/19] devicetree.bbclass: Combine stderr into stdout to see actual dtc error Armin Kuster
2019-06-24 3:54 ` [Warrior][ 06/19] context.py: fix skipping function Armin Kuster
2019-06-24 3:54 ` [Warrior][ 07/19] ptest-runner: update SRCREV to latest HEAD on ptest-runner2 repo Armin Kuster
2019-06-24 3:54 ` [Warrior][ 08/19] ptest-runner: enable child procs as session leader Armin Kuster
2019-06-24 3:54 ` [Warrior][ 09/19] openssl: fix failure of ptest test_shlibload Armin Kuster
2019-06-24 3:54 ` [Warrior][ 10/19] manifest.py: fix test_SDK_manifest_entries Armin Kuster
2019-06-24 3:54 ` [Warrior][ 11/19] rootfs: Fix dependency for every dpkg run Armin Kuster
2019-06-24 3:54 ` [Warrior][ 12/19] oeqa/logparser: ignore test failure commentary Armin Kuster
2019-06-24 3:54 ` [Warrior][ 13/19] uninative: Update to 2.6 release Armin Kuster
2019-06-24 3:54 ` [Warrior][ 14/19] libxslt: Fix CVE-2019-11068 Armin Kuster
2019-06-24 3:54 ` [Warrior][ 15/19] texinfo-dummy-native: A little clean up of template.py Armin Kuster
2019-06-24 7:38 ` Adrian Bunk
2019-06-24 10:22 ` Richard Purdie
2019-06-24 12:42 ` Peter Kjellerstedt [this message]
2019-06-24 3:54 ` [Warrior][ 16/19] texinfo-dummy-native: Rewrite template.py to use argparse Armin Kuster
2019-06-24 3:54 ` [Warrior][ 17/19] package.bbclass: Clean up writing of runtime pkgdata files Armin Kuster
2019-06-24 3:54 ` [Warrior][ 18/19] wpa-supplicant: Fix CVE-2019-9494 CVE-2019-9495 CVE-2019-9496 CVE-2019-9497 CVE-2019-9498 CVE-2019-9499 CVE-2019-11555 Armin Kuster
2019-06-24 3:54 ` [Warrior][ 19/19] gpg_sign/selftest: Fix secmem parameter handling Armin Kuster
2019-06-24 15:55 ` [Warrior][ 00/19] patch review Tom Rini
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=5ddcbbe68f00435fa57cf14b59e4863d@XBOX04.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=akuster808@gmail.com \
--cc=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox