From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 2/2] tools: make genboardscfg.py compatible with Python 2.5
Date: Sat, 23 Aug 2014 08:44:49 -0400 [thread overview]
Message-ID: <20140823124449.GH19374@bill-the-cat> (raw)
In-Reply-To: <20140822150130.A091.AA925319@jp.panasonic.com>
On Fri, Aug 22, 2014 at 03:01:30PM +0900, Masahiro Yamada wrote:
> Tom,
>
>
> I noticed this patch's gone to RFC.
>
> Did you decide to drop python2.5 from support?
>
> If so, I will use "except ... as ..." and "with ... as ..."
> statements in my other patches.
So, I'm not 100% sure just yet how to handle this. I'm biased about
supporting python2.6 since that's what my big compute resources are
pinned to (until Ubuntu 10.04 LTS is no longer supported). And I'm
making them switch to buildman too. It's also possible (and encouraged,
relatively speaking, by the admins) to add required new software
/over/there. So how hard is it to keep what MAKEALL/buildman needs (so
genboardscfg.py) and maybe even convert buildman to python2.5-or-later ?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140823/d8823f62/attachment.pgp>
next prev parent reply other threads:[~2014-08-23 12:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 10:23 [U-Boot] [RFC PATCH v2 0/2] Make Python scripts compatible with older versions Masahiro Yamada
2014-08-04 10:23 ` [U-Boot] [RFC PATCH v2 1/2] kconfig: make multiconfig.py compatible with Python 2.4 Masahiro Yamada
2014-08-04 10:23 ` [U-Boot] [RFC PATCH v2 2/2] tools: make genboardscfg.py compatible with Python 2.5 Masahiro Yamada
2014-08-22 6:01 ` Masahiro Yamada
2014-08-22 6:18 ` Masahiro Yamada
2014-08-23 12:44 ` Tom Rini [this message]
2014-08-25 1:53 ` Masahiro Yamada
2014-08-04 10:40 ` [U-Boot] [RFC PATCH v2 0/2] Make Python scripts compatible with older versions Simon Glass
2014-08-04 11:21 ` Igor Grinberg
2014-08-04 12:00 ` Masahiro Yamada
2014-08-04 12:59 ` Masahiro Yamada
2014-08-04 13:17 ` Igor Grinberg
2014-08-04 13:28 ` Masahiro Yamada
2014-08-07 10:57 ` Tom Rini
2014-08-07 13:17 ` Igor Grinberg
2014-08-07 16:57 ` Tom Rini
2014-08-07 17:33 ` Stephen Warren
2014-08-07 17:53 ` Tom Rini
2014-08-10 8:49 ` Igor Grinberg
2014-08-10 11:14 ` Tom Rini
2014-08-11 10:18 ` Igor Grinberg
2014-08-11 13:12 ` Tom Rini
2014-08-11 23:03 ` Masahiro YAMADA
2014-08-12 1:53 ` Tom Rini
2014-08-18 4:45 ` Masahiro Yamada
2014-08-11 16:58 ` Stephen Warren
2014-08-12 10:32 ` Igor Grinberg
2014-08-04 13:50 ` Tom Rini
2014-08-05 2:05 ` Yan, Miao
2014-08-05 14:18 ` 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=20140823124449.GH19374@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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