From: Maxime Ripard <ripard@archos.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] python: Add needed extra patches.
Date: Wed, 15 Dec 2010 21:12:02 +0100 [thread overview]
Message-ID: <4D092112.5010908@archos.com> (raw)
In-Reply-To: <20101204010045.0a7a2769@surf>
Hi Thomas,
On 04/12/2010 01:00, Thomas Petazzoni wrote:
> Could you provide a bit more details on why those patches are needed ?
> We generally want each patch to have a description in the patch itself,
> together with the name of the patch author, or the patch source if it
> has been borrowed from some other place.
Here is a new set of patches with details either as header or comments.
Is it ok for you ?
Regards,
Maxime
____________________________________________________________________________
This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to which they are
addressed. Access to this e-mail by anyone else is unauthorised. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited. E-mail
messages are not necessarily secure. Archos does not accept responsibility
for any changes made to this message after it was sent.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-python-Port-the-python2.4-patches-to-2.7.patch
Type: text/x-patch
Size: 22613 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101215/1a9c62de/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-python-Add-the-needed-patches-to-compile-python2.7-i.patch
Type: text/x-patch
Size: 3522 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101215/1a9c62de/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-python-Fix-make-install-Workaround-python-s-bug-1669.patch
Type: text/x-patch
Size: 1488 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101215/1a9c62de/attachment-0005.bin>
next prev parent reply other threads:[~2010-12-15 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 8:26 [Buildroot] [PATCH 0/4] Move to Python 2.7 Maxime Ripard
2010-10-12 8:26 ` [Buildroot] [PATCH 1/4] python: Move to version 2.7 Maxime Ripard
2010-10-12 8:26 ` [Buildroot] [PATCH 2/4] python: Port the existing patches to python2.7 Maxime Ripard
2010-10-12 8:26 ` [Buildroot] [PATCH 3/4] python: Add needed extra patches Maxime Ripard
2010-12-04 0:00 ` Thomas Petazzoni
2010-12-15 20:12 ` Maxime Ripard [this message]
2010-10-12 8:26 ` [Buildroot] [PATCH 4/4] python: Fix make install (Workaround python's bug #1669349) Maxime Ripard
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=4D092112.5010908@archos.com \
--to=ripard@archos.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