From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: FYI: merge to archer-tromey-python
Date: Fri, 13 Aug 2010 20:55:00 -0000 [thread overview]
Message-ID: <m38w4axmf6.fsf@fleche.redhat.com> (raw)
I did a merge from master to archer-tromey-python today. Then I removed
a few things from the branch that are no longer relevant. (There are
still a few things that remain that are not used, I didn't bother
changing everything back.)
Looking at the resulting diff, I see that the "gdb --python" stuff is
pretty half-baked.
There are some minor test suite differences. I don't know if we care.
Then the remaining diffs are really just .py scripts. Joel took a stab
at upstreaming one of these; I think we can probably work through them
one by one. A few of them (the backtrace ones) need some fixes, but
some of them are basically ok.
Tom
reply other threads:[~2010-08-13 20:55 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=m38w4axmf6.fsf@fleche.redhat.com \
--to=tromey@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).