From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Robert Lupton the Good <rhl@astro.princeton.edu>, gdb@sourceware.org
Subject: Re: Option parsing in gdb python
Date: Thu, 27 Oct 2011 17:01:00 -0000 [thread overview]
Message-ID: <m3vcrafk00.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20111024212805.GP335@adacore.com> (Joel Brobecker's message of "Mon, 24 Oct 2011 14:28:05 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> PS: As far as I know, I think that our position is that we support
Joel> versions 2.4 to 2.7.
Yes, or at least that is the current concrete expression of the rule "we
support whatever people care enough about to submit patches to keep
working".
Tom
next prev parent reply other threads:[~2011-10-27 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1319403653.11425.ezmlm@sourceware.org>
2011-10-24 21:28 ` Robert Lupton the Good
2011-10-24 21:35 ` Joel Brobecker
2011-10-25 2:58 ` Robert Lupton the Good
2011-10-27 17:01 ` Tom Tromey [this message]
2011-10-27 19:32 ` Tom Tromey
2011-10-22 1:22 Robert Lupton the Good
2011-10-23 21:00 ` 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=m3vcrafk00.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=rhl@astro.princeton.edu \
/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).