Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: GDB Focus Group at the 2008 GCC Summit
Date: Sun, 22 Jun 2008 06:08:00 -0000	[thread overview]
Message-ID: <20080622020754.z4ur1xzb40k0cs00@imap.linux.ibm.com> (raw)
In-Reply-To: <20080619190942.GA3744@adacore.com>

Zitat von Joel Brobecker <brobecker@adacore.com>:
> Hello,

Hi,

> we had a couple of 45min sessions where we discussed various items
> related to GDB. I took some brief notes, although I might have forgotten
> one or two. Anyway, here is what I wrote:

Thanks.

> | * Next GDB Release:
> |     For people really interested in trying it out before the official
> |     release, perhaps either:
> |       - Announce various nightly tarballs that contain the features
> |       - Or perhaps create a 6.9 branch but never release 6.9. Just
> |         make various pre-releases 6.8.90, 6.8.91, etc.

I was going to say that I prefer the second option, with this reasoning:
when we have the new interesting features in HEAD and in a reasonably
feature-complete state, we could branch and point people at that so that they
can try it out and at the same time be isolated from unrelated unstable
development.

On the other hand, CVS HEAD has pretty much always been reliable to me, so in
the case of GDB that general "release engineering" logic doesn't need to be
used. So I guess the first option is good enough for us, and will save some
branch maintenance work.

> |     Suggestion: Make sure that the distros build GDB with Python
> |     enabled when support is provided in a release.

I think that this is a no-brainer for the distros...

By the way, thanks for organizing the get-together lunch!

And thanks to Daniel for organizing the BoF.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2008-06-22  6:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 19:10 Joel Brobecker
2008-06-22  6:08 ` Thiago Jung Bauermann [this message]
2008-06-22 11:52 ` Nick Roberts
2008-06-22 13:53   ` Joel Brobecker
2008-06-23 15:17   ` Tom Tromey
2008-06-23 17:35     ` Jim Ingham
2008-06-23 21:55     ` Nick Roberts
2008-06-23 15:16 ` Tom Tromey
2008-06-26  0:24   ` Tom Tromey
2008-07-03  3:27   ` Thiago Jung Bauermann
2008-07-03  8:12     ` Andreas Schwab
2008-07-03 12:35     ` Daniel Jacobowitz
2008-07-03 14:28       ` Thiago Jung Bauermann
2008-07-04  2:33       ` Tom Tromey
2008-07-04  3:19         ` Daniel Jacobowitz
2008-06-23 21:46 ` Jason Molenda
2008-06-23 22:22   ` Nick Roberts
2008-06-24 21:18     ` Nick Roberts
2008-06-25  6:56       ` [MI] changing breakpoint location (Was: GDB Focus Group at the 2008 GCC Summit) Vladimir Prus
2008-06-23 22:09 ` GDB Focus Group at the 2008 GCC Summit Mark Kettenis
2008-06-23 22:26   ` Joel Brobecker
2008-06-24  8:35   ` Andrew STUBBS
2008-06-24  8:56     ` Andreas Schwab
2008-06-24 18:12     ` Michael Snyder
2008-06-24 18:28     ` Daniel Jacobowitz
2008-06-24 19:33     ` Dave Korn

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=20080622020754.z4ur1xzb40k0cs00@imap.linux.ibm.com \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@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