From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, antoine.tremblay@ericsson.com,
mishra.nitish.88@gmail.com
Subject: Re: GDB 8.0 release / imminent branching? (2017-04-10)
Date: Wed, 12 Apr 2017 05:27:00 -0000 [thread overview]
Message-ID: <87wpaqxkk6.fsf@redhat.com> (raw)
In-Reply-To: <20170411011802.s24zz4pygnt2qoyg@adacore.com> (Joel Brobecker's message of "Mon, 10 Apr 2017 18:18:02 -0700")
On Monday, April 10 2017, Joel Brobecker wrote:
> Hello,
>
> We're now about 4 weeks after our tentative branching date, and
> I am concerned that if we continue to wait for some of the pending
> issues to be resolved, we'll have new issues appearing on master
> that'll might delay the branching further. So I'd like to propose
> we branch in the next couple of days, and then backport fixes,
> so as to stabilize the branch.
Yay :-).
[...]
> And finally, there is the build-bot. I'm having trouble using
> the interface and understanding whether the current overall
> state is rather positive or negative. Sergio, would you be able
> to help me? If all good, I could create the branch with a SHA1
> that you'd give me!
Sure thing. I'll take a look this Wednesday and let you guys know if
there's anything suspicious there.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2017-04-12 5:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 1:18 Joel Brobecker
2017-04-11 7:47 ` Yao Qi
2017-04-11 14:21 ` Andreas Arnez
2017-04-11 15:39 ` Yao Qi
2017-04-12 15:38 ` Joel Brobecker
2017-04-11 15:41 ` Eli Zaretskii
2017-04-12 14:18 ` Joel Brobecker
2017-04-11 19:00 ` Antoine Tremblay
2017-04-12 5:27 ` Sergio Durigan Junior [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=87wpaqxkk6.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mishra.nitish.88@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