From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Thu, 23 Nov 2017 17:32:00 -0000 [thread overview]
Message-ID: <8f0b5d0f-40a7-b3eb-89c8-bdd672d8046a@redhat.com> (raw)
In-Reply-To: <20171123165008.hurbxfju2s27qhbk@adacore.com>
On 11/23/2017 04:50 PM, Joel Brobecker wrote:
>> Can we consider delaying the branching some more time? E.g., at least
>> a week? I'm not certain I'll be able to address all of Keith's comments
>> on the wildmatching series this week (and I'd very much like to get it in
>> because the sooner we have that in a release, the sooner we can move
>> gdb to a C++ namespace), and also, a lot of folks in the US are off for
>> thanksgiving this week (including Keith :-). There are a few other pending
>> patches that I'd like to try to get in (patches that have already been posted
>> but are waiting for review, e.g., DWARF5 indexes, Keith's inline
>> breakpoint and ptype patches, etc.), and next Monday is just looking too
>> tight.
>
> Absolutely.
>
> There are a number of patches that people would like to get in, and
> I won't create the branch until I have at least given those a chance
> to get in. Using the branch to help us decide which changes we want
> to focus is good, but I don't want people to feel pressured into
> rush them and/or cutting corners. The calendar is only a reference
> for us, but other than that, we only create the branch when we feel
> this is a good time.
>
Thanks Joel. I'll keep you posted.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-11-23 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55 ` Joel Brobecker
2017-11-28 19:44 ` Ulrich Weigand
2017-11-28 20:32 ` Pedro Alves
2017-11-29 13:20 ` Pedro Alves
2017-11-29 21:00 ` Joel Brobecker
2017-11-29 21:49 ` Pedro Alves
2017-11-29 22:20 ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves
2017-11-27 22:20 ` Joel Brobecker
2017-11-27 22:41 ` Pedro Alves
2017-11-29 20:56 ` Joel Brobecker
2017-11-29 22:20 ` Pedro Alves
2017-11-29 22:46 ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi
2017-11-27 22:06 ` Joel Brobecker
2017-11-27 22:14 ` Joel Brobecker
2017-11-28 12:38 ` Yao Qi
2017-11-29 20:58 ` Joel Brobecker
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23 ` Joel Brobecker
2017-11-28 17:08 ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50 ` Joel Brobecker
2017-11-23 17:32 ` Pedro Alves [this message]
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=8f0b5d0f-40a7-b3eb-89c8-bdd672d8046a@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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