Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 ] python3: Port python2 patches to reduce the interpreter size
Date: Wed, 3 Jul 2013 11:20:41 +0200	[thread overview]
Message-ID: <20130703092041.GH2969@lukather> (raw)
In-Reply-To: <CANxTyt52OPdj0gmCZ8narNkgSpAZahnWR_-iuTHTe+nvHsjvHQ@mail.gmail.com>

Hi Danomi,

On Mon, Jul 01, 2013 at 03:29:59PM -0400, Danomi Manchego wrote:
> I noticed that most the original python3-3.3-* patches got renamed to
> python3-*.  But one did not, python3-3.3-012-old-stdlib-cache.patch.  This
> feels like an oversight - was it supposed to be renamed, or deleted maybe?

Yeah, sorry, I somehow forgot to rename that patch.

Do you want to do it?

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130703/4ef63afe/attachment-0001.asc>

  parent reply	other threads:[~2013-07-03  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:36 [Buildroot] [PATCHv3 ] python3: Port python2 patches to reduce the interpreter size Maxime Ripard
2013-05-29 14:56 ` Samuel Martin
2013-05-29 15:17   ` Thomas Petazzoni
2013-06-07  8:57     ` Maxime Ripard
2013-06-07  9:52       ` Samuel Martin
2013-06-07 10:09         ` Maxime Ripard
2013-06-29  8:22 ` Peter Korsgaard
2013-07-01 19:29   ` Danomi Manchego
2013-07-02  9:02     ` Peter Korsgaard
2013-07-03  9:20     ` Maxime Ripard [this message]
2013-07-03 14:18       ` Peter Korsgaard

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=20130703092041.GH2969@lukather \
    --to=maxime.ripard@free-electrons.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