From: Joel Brobecker <brobecker@adacore.com>
To: Nick Bull <nicholaspbull@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB 7.7 branching on Monday?
Date: Wed, 25 Dec 2013 02:47:00 -0000 [thread overview]
Message-ID: <20131225024733.GH4605@adacore.com> (raw)
In-Reply-To: <CABbKtXuZ_-ckJmmcyhfcBfrob67_90oaP6e-jE=W=+Hkb5Lofw@mail.gmail.com>
> Is it possible to get this Python events patch in under the wire?
>
> http://sourceware.org/ml/gdb-patches/2013-12/msg00505.html
>
> It's been through a couple of rounds of review and has no outstanding
> issues that I know of.
I'd love to get this one in 7.7, but at the same time, it's hard
justifying delaying a branch for a non-critical failure.
The good news is that there is little to no activity at the moment,
so there is no point in me creating the branch now. Creating it
after New Year will prevent the need for updating the year ranges
in the copyright headers twice. And that will give you more time
to get the patch in.
I took a quick look at your patch; one of the trivial things I noticed
is that many new functions and new types are missing documentation.
If you add those and resend a patch, that'll have the nice property
if implicitly pinging the maintainers. Also, feel free to ping on
your patch a week or two after submission, and every week thereafter.
--
Joel
next prev parent reply other threads:[~2013-12-25 2:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 21:22 Nick Bull
2013-12-25 2:47 ` Joel Brobecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-19 17:59 Joel Brobecker
2013-12-19 18:06 ` H.J. Lu
2013-12-19 18:22 ` Joel Brobecker
2013-12-19 18:27 ` H.J. Lu
2013-12-19 21:52 ` Mark Kettenis
2013-12-19 22:29 ` H.J. Lu
2013-12-19 20:31 ` Sergio Durigan Junior
2013-12-20 3:28 ` Joel Brobecker
2013-12-20 3:37 ` Sergio Durigan Junior
2013-12-25 4:48 ` Sergio Durigan Junior
2013-12-28 3:11 ` Joel Brobecker
2013-12-23 8:01 ` Joel Brobecker
2014-01-07 2:54 ` Joel Brobecker
2014-01-07 23:44 ` Pierre Muller
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=20131225024733.GH4605@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nicholaspbull@gmail.com \
/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