From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Python not optional?
Date: Wed, 20 Aug 2008 18:53:00 -0000 [thread overview]
Message-ID: <m34p5fpxbd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200808201429.m7KETPMV006783@brahms.sibelius.xs4all.nl> (Mark Kettenis's message of "Wed\, 20 Aug 2008 16\:29\:25 +0200 \(CEST\)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> I always assumed that the Python scripting support would be optional.
It is supposed to be.
Mark> Luckily this isn't too difficult to fix; the attached rough
Mark> diff does the job, but might need a bit of cleanup.
I will send a different patch shortly.
It would be helpful if you could mention the errors you saw.
Tom
next prev parent reply other threads:[~2008-08-20 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 18:37 Mark Kettenis
2008-08-20 18:53 ` Tom Tromey [this message]
2008-08-20 18:56 ` Mark Kettenis
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=m34p5fpxbd.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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