From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Mark Wielaard <mark@klomp.org>,
Jonas Maebe <jonas.maebe@elis.ugent.be>,
Jim Ingham <jingham@apple.com>,
gdb@sourceware.org
Subject: Re: [ANNOUNCEMENT] GDB 7.0 release process created
Date: Tue, 22 Sep 2009 17:10:00 -0000 [thread overview]
Message-ID: <20090922171018.GB14971@bromo.med.uc.edu> (raw)
In-Reply-To: <20090922155557.GA13560@caradoc.them.org>
On Tue, Sep 22, 2009 at 11:55:57AM -0400, Daniel Jacobowitz wrote:
> I don't mind if folks want to have this discussion somewhere else, but
> it is off-topic for the GDB list; please don't have it here. Thanks.
>
> --
> Daniel Jacobowitz
> CodeSourcery
Daniel,
I assume you mean the discussion of the FSF legal issues and not
the discussion of what patches are required for gdb 7.0 to function
on MacOS X (which would be entirely relevant to the list).
Jack
next prev parent reply other threads:[~2009-09-22 17:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 22:20 Joel Brobecker
2009-09-18 0:42 ` Tom Tromey
2009-09-18 0:49 ` Hui Zhu
2009-09-20 2:54 ` Jack Howarth
2009-09-20 3:50 ` Paul Pluzhnikov
2009-09-20 14:32 ` Joel Brobecker
2009-09-20 15:02 ` Paul Pluzhnikov
2009-09-20 15:28 ` Joel Brobecker
2009-09-20 16:14 ` Paul Pluzhnikov
2009-09-20 17:12 ` Joel Brobecker
2009-09-20 17:36 ` Jack Howarth
2009-09-20 17:40 ` Joel Brobecker
2009-09-20 18:37 ` Paul Pluzhnikov
2009-09-20 19:12 ` Jack Howarth
2009-09-20 20:22 ` Paul Pluzhnikov
2009-09-21 4:34 ` Joel Brobecker
2009-09-21 12:57 ` Jack Howarth
2009-09-21 13:36 ` Jonas Maebe
2009-09-21 13:46 ` Jack Howarth
2009-09-21 13:55 ` Jonas Maebe
2009-09-21 19:19 ` Jim Ingham
2009-09-22 12:59 ` Mark Wielaard
2009-09-22 13:30 ` Jonas Maebe
2009-09-22 14:31 ` Mark Wielaard
2009-09-22 15:56 ` Daniel Jacobowitz
2009-09-22 17:10 ` Jack Howarth [this message]
2009-09-22 17:34 ` Daniel Jacobowitz
2009-09-22 18:11 ` Mark Wielaard
2009-09-22 19:28 ` Tom Tromey
2009-09-21 13:26 ` Jack Howarth
2009-09-20 16:19 ` Paul Pluzhnikov
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=20090922171018.GB14971@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gdb@sourceware.org \
--cc=jingham@apple.com \
--cc=jonas.maebe@elis.ugent.be \
--cc=mark@klomp.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