From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Subject: Merged master into archer-tromey-python (and a few notes)
Date: Tue, 13 Jul 2010 08:48:00 -0000 [thread overview]
Message-ID: <4C3C2868.5010506@redhat.com> (raw)
I've merged master in archer-tromey-python
http://sourceware.org/ml/archer-commits/2010-q3/msg00020.html
A few notes as this was a big merge. During the last few months we've
been working on getting the Python API accepted upstream. The good
news is that most of it has been accepted and committed. However
during upstream review some of the API was changed. This was
unfortunate, but inevitable. With this merge of 'master' the upstream
version of the API replaces the old Archer API. I don't think the
changes are too big, so if you are a consumer of the
archer-tromey-python branch and get stuck with a change, find us on
irc (at freenode, #gdb) or reply here. We can help you out on any
changes you may need to make.
There are some patches that have not been submitted yet. We'll
endeavour to get these in soon. To that end I will probably be
committing a few clean-up commits to archer-tromey-python that will
normalize the difference between upstream and archer-tromey-python.
I think Jan is also going to remove the type reference counting
patch-set. This is just so we can really make sure we have not missed
something important before we close the archer-tromey-python branch.
Cheers,
Phil
reply other threads:[~2010-07-13 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C3C2868.5010506@redhat.com \
--to=pmuldoon@redhat.com \
--cc=archer@sourceware.org \
/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).