From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [gdb-7.0 release] 2009-09-02 status and proposed plan
Date: Thu, 03 Sep 2009 20:12:00 -0000 [thread overview]
Message-ID: <m363bzg55s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090903192552.GC4379@adacore.com> (Joel Brobecker's message of "Thu, 3 Sep 2009 12:25:52 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Tom> I'm ok with the simple rm + add approach.
Joel> I agree. Let's apply the patch ASAP. Do you happen to have a
Joel> rebased version of the patch somewhere in archer, by any chance?
No, I'm afraid not.
Tom> There are a number of other unreviewed patches. I can try to make a
Tom> list if that would be helpful.
Joel> I think it would. We need to draw our attention to everything that
Joel> needs to be done before branching.
My list is probably incomplete, since I have not been systematic about
tracking patches. That said, patch submitters do bear some burden to
ping their patches and to otherwise irritate a maintainer into
responding ;)
* The catch syscall patches. I didn't dig up the URLs for these.
* Caz Yokoyama's kgdb patch. I don't think the most recent one was ever
reviewed.
http://permalink.gmane.org/gmane.comp.gdb.patches/50989
* Watchpoint on an unloaded shared library
http://permalink.gmane.org/gmane.comp.gdb.patches/46187
http://permalink.gmane.org/gmane.comp.gdb.patches/46290
* gdb.objc/objcdecode.exp test error
http://permalink.gmane.org/gmane.comp.gdb.patches/47073
* Xtensa backtrace
http://permalink.gmane.org/gmane.comp.gdb.patches/48614
* Fix breakpoints when several source files have the same name
http://permalink.gmane.org/gmane.comp.gdb.patches/49047
* Jonas Maebe's calling convention patch, pinged twice.
http://permalink.gmane.org/gmane.comp.gdb.patches/49467
* Nathan Froyd's internal error patch, pinged once.
http://permalink.gmane.org/gmane.comp.gdb.patches/50458
* Paul Pluzhnikov's pending patches.
He pinged these recently:
http://sourceware.org/ml/gdb-patches/2009-08/msg00372.html
http://sourceware.org/ml/gdb-patches/2009-08/msg00437.html
* Jan Kratochvil's watchpoint series.
First one: http://permalink.gmane.org/gmane.comp.gdb.patches/51128
* Sami Wagiaalla's namespace patches.
http://permalink.gmane.org/gmane.comp.gdb.patches/51166
http://permalink.gmane.org/gmane.comp.gdb.patches/51167
* Use external editor in 'commands' command
http://permalink.gmane.org/gmane.comp.gdb.patches/51394
* Keith's recent dwarf2/c++ patches.
There are a couple other biggish pending things I remember: Vala and D
support, but those are stalled for some reason on the submitter side
(lack of activity or waiting for paperwork).
I've meant to review some of these, but of course it is tough to get to
them all. And, there are several in here that I won't review as I don't
have the necessary expertise. I'm not sure whether any of these require
paperwork, either.
Joel> I understand that someone might be disappointed that his patch
Joel> does not make the next release, but should we really delay this
Joel> further for things like minor enhancements for instance?
I just wanted to encourage maintainers to make an extra effort.
I agree we shouldn't delay the release for anything minor.
Joel> I propose the following approach: Let's commit to reviewing promptly
Joel> all patches that are posted before branch time. Patches that are safe
Joel> for the branch will be added and part of the 7.0.1 release. Others
Joel> should not be checked in at such a late stage anyway (IMO). What do
Joel> you think?
Yes, sounds good to me.
Tom
next prev parent reply other threads:[~2009-09-03 20:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 16:44 Joel Brobecker
2009-09-02 17:09 ` Jack Howarth
2009-09-02 17:18 ` Joel Brobecker
2009-09-03 8:58 ` Tristan Gingold
2009-09-02 19:28 ` Tom Tromey
2009-09-03 3:18 ` Eli Zaretskii
2009-09-03 3:30 ` Hui Zhu
2009-09-04 15:48 ` Sérgio Durigan Júnior
2009-09-03 19:28 ` Joel Brobecker
2009-09-03 19:53 ` Tom Tromey
2009-09-03 21:35 ` Joel Brobecker
2009-09-04 15:44 ` Tom Tromey
2009-09-04 21:34 ` Sérgio Durigan Júnior
2009-09-04 21:37 ` Sérgio Durigan Júnior
2009-09-04 21:37 ` Sérgio Durigan Júnior
2009-09-03 19:26 ` Joel Brobecker
2009-09-03 20:12 ` Tom Tromey [this message]
2009-09-03 20:39 ` Matt Rice
2009-09-03 21:43 ` Joel Brobecker
2009-09-04 15:36 ` Doug Evans
2009-09-03 2:05 ` Hui Zhu
2009-09-03 19:31 ` Joel Brobecker
2009-09-05 0:25 ` Joel Brobecker
2009-09-05 8:13 ` Mark Kettenis
2009-09-05 8:24 ` Jonas Maebe
2009-09-05 15:58 ` Eli Zaretskii
2009-09-03 4:06 ` Doug Evans
2009-09-03 15:54 ` Paul Pluzhnikov
2009-09-03 16:00 ` Pierre Muller
2009-09-03 16:11 ` Paul Pluzhnikov
2009-09-04 10:20 ` Pierre Muller
2009-09-04 15:07 ` Paul Pluzhnikov
2009-09-07 14:58 ` Pierre Muller
[not found] ` <8ac60eac0909072137g41f7b1f8q2e9e1e6d6d161fc5@mail.gmail.com>
[not found] ` <000301ca309f$35d475d0$a17d6170$@u-strasbg.fr>
2009-09-08 20:41 ` Paul Pluzhnikov
2009-09-03 19:33 ` Joel Brobecker
2009-09-04 15:25 ` Paul Pluzhnikov
2009-09-04 17:59 ` Paul Pluzhnikov
2009-09-04 18:03 ` Doug Evans
2009-09-05 0:29 ` Joel Brobecker
2009-09-14 17:43 ` Paul Pluzhnikov
2009-09-14 17:52 ` Joel Brobecker
2009-09-14 18:20 ` Paul Pluzhnikov
2009-09-15 20:28 ` Paul Pluzhnikov
2009-09-03 18:34 ` Anirban Sinha
2009-09-04 23:07 ` Joel Brobecker
2009-09-16 6:47 ` Hui Zhu
[not found] ` <F7CE05678329534C957159168FA70DEC5153684DC5@EUSAACMS0703.eamcs.ericsson.se>
2009-09-17 1:02 ` Joel Brobecker
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=m363bzg55s.fsf@fleche.redhat.com \
--to=tromey@redhat.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