From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/python3-setuptools: new package
Date: Mon, 14 Jan 2019 20:59:59 +0100 [thread overview]
Message-ID: <20190114205959.627d6fd2@windsurf> (raw)
In-Reply-To: <eeadf2d8-96fd-a183-fb00-45fe67af51e2@mind.be>
Hello,
On Mon, 14 Jan 2019 19:31:05 +0100, Arnout Vandecappelle wrote:
> On 28/12/2018 18:01, Thomas Petazzoni wrote:
> > +# Please keep in sync with
> > +# package/python-setuptools/python-setuptools.mk
>
> It is in fact more important to have this comment in python-setuptools.mk,
> because that is the one that most likely will be bumped...
I just submitted a patch doing this, you're Cc'ed. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-14 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 17:01 [Buildroot] [PATCH 0/3] Prepare Python support for top-level parallel build Thomas Petazzoni
2018-12-28 17:01 ` [Buildroot] [PATCH 1/3] package/python3-setuptools: new package Thomas Petazzoni
2018-12-29 15:13 ` Asaf Kahlon
2018-12-31 18:32 ` Yegor Yefremov
2019-01-01 10:31 ` Thomas Petazzoni
2019-01-14 18:31 ` Arnout Vandecappelle
2019-01-14 19:59 ` Thomas Petazzoni [this message]
2018-12-28 17:01 ` [Buildroot] [PATCH 2/3] package/pkg-python: use host-python3-setuptools when needed Thomas Petazzoni
2018-12-29 15:15 ` Asaf Kahlon
2018-12-31 18:29 ` Yegor Yefremov
2019-01-01 10:31 ` Thomas Petazzoni
2018-12-28 17:01 ` [Buildroot] [PATCH 3/3] package/pkg-python: use --single-version-externally-managed for host setuptools Thomas Petazzoni
2018-12-29 15:16 ` Asaf Kahlon
2018-12-31 18:30 ` Yegor Yefremov
2019-01-01 10:31 ` Thomas Petazzoni
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=20190114205959.627d6fd2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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