From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Paul_Koning@dell.com
Subject: [commit] [patchv2] Fix Python 3 build error on 32-bit hosts
Date: Wed, 04 Feb 2015 19:34:00 -0000 [thread overview]
Message-ID: <20150204193417.GA12728@host1.jankratochvil.net> (raw)
In-Reply-To: <54D27294.8010009@redhat.com>
On Wed, 04 Feb 2015 20:27:16 +0100, Pedro Alves wrote:
> Distros will be backporting Python fixes, not API/ABI breaking changes.
Adding a new typedef (in the library namespace) I do not find as an API
breakage (for correctly written applications).
> OK.
Checked in:
881d5d5db08ee6b343e1f1fc560d785fed29428e
Thanks,
Jan
next prev parent reply other threads:[~2015-02-04 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:43 [patch] " Jan Kratochvil
2015-02-04 18:39 ` Paul_Koning
2015-02-04 18:58 ` Pedro Alves
2015-02-04 19:08 ` Pedro Alves
2015-02-04 19:20 ` [patchv2] " Jan Kratochvil
2015-02-04 19:27 ` Pedro Alves
2015-02-04 19:34 ` Jan Kratochvil [this message]
2015-02-04 19:42 ` [commit] " Pedro Alves
2015-02-04 19:51 ` Phil Muldoon
2015-02-04 21:06 ` Paul_Koning
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=20150204193417.GA12728@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=Paul_Koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).