From: Przemyslaw Wrzos <przemyslaw.wrzos@calyptech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #6 (deadline February 2)
Date: Tue, 21 Jan 2014 13:53:57 +1100 [thread overview]
Message-ID: <000601cf1654$07ca5c00$175f1400$@calyptech.com> (raw)
In-Reply-To: <CAAXf6LX2yqbapp6GBuN5qoT1R93CGD3NCLguY8fQhFoApJz2uw@mail.gmail.com>
Hello Thomas,
On Tue, 21 Jan 2014 at 08:06:25, Thomas De Schampheleire wrote:
> In particular, I'm interested in knowing if the original contributor is
> still interested by the patch, or if someone else is interested in
> adopting the patch and sending an updated version, or if the patch no
> longer makes sense due to other changes made in Buildroot.
...
> [1/1] python: fix to ensure libpython is stripped Przemyslaw Wrzos
> <przemyslaw.wrzos@calyptech.com>
http://patchwork.ozlabs.org/patch/220024
I'd still like to see this one included in some form. For embedded systems
that count their image sizes in the tens of megabytes, this patch can make
a not insignificant difference.
The patch still applies as is to the latest source tree. Let me know if
anything else need to be done from my end.
Cheers,
Przemyslaw Wrzos
next prev parent reply other threads:[~2014-01-21 2:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:06 [Buildroot] Patchwork oldest patches cleanup #6 (deadline February 2) Thomas De Schampheleire
2014-01-21 2:53 ` Przemyslaw Wrzos [this message]
2014-01-21 7:46 ` Thomas De Schampheleire
2014-01-23 3:43 ` Przemyslaw Wrzos
2014-01-21 7:58 ` Stephan Hoffmann
2014-01-21 8:18 ` Thomas De Schampheleire
2014-01-21 9:39 ` Stephan Hoffmann
2014-01-21 10:20 ` Thomas De Schampheleire
2014-01-21 9:02 ` Fabio Porcedda
2014-01-21 9:05 ` Thomas De Schampheleire
2014-01-22 22:10 ` Steve Calfee
2014-01-23 14:06 ` Thomas De Schampheleire
2014-01-27 20:07 ` Thomas De Schampheleire
2014-02-03 9:52 ` Thomas De Schampheleire
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='000601cf1654$07ca5c00$175f1400$@calyptech.com' \
--to=przemyslaw.wrzos@calyptech.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 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.