From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, keiths@redhat.com
Subject: Re: GDB 7.10 release 2015-07-17 status update?
Date: Fri, 17 Jul 2015 18:35:00 -0000 [thread overview]
Message-ID: <20150717183541.GD7406@adacore.com> (raw)
In-Reply-To: <20150717182842.GA7050@host1.jankratochvil.net>
> > - [GCC review/Jan] PR compile/18485 (set debug compile: Display GCC driver
> > filename)
> > - [GCC review/Jan] PR compile/18486 (Add 'set compile-gcc')
> >
> > If the reason for it being a "Maybe" is time, we can probably give you
> > a little extra time (see below).
>
> I have pinged those now:
> ping: [PATCH v3 1/4] libcc1: Introduce GCC_FE_VERSION_1
> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01563.html
>
> But I do not think it matters much, there are other more important parts of
> the 'compile' project.
>
> The release really should not be delayed in any way for it.
> It could be also already rejected that 7.11 will be enough for it.
OK, in that case, let's just delete those entries from the wiki,
and if you get the patches in master in time, you can always ask
for the patches to also be ported to 7.10.
--
Joel
next prev parent reply other threads:[~2015-07-17 18:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 17:53 Joel Brobecker
2015-07-17 18:14 ` Luis Machado
2015-07-17 18:32 ` Joel Brobecker
2015-07-17 18:38 ` Luis Machado
2015-07-17 19:06 ` Eli Zaretskii
2015-07-17 20:48 ` Joel Brobecker
2015-07-17 20:57 ` Luis Machado
2015-07-20 10:13 ` Iain Buclaw
2015-07-21 17:16 ` Joel Brobecker
2015-07-17 19:04 ` Eli Zaretskii
2015-07-17 19:03 ` Eli Zaretskii
2015-07-24 9:26 ` Pedro Alves
2015-07-24 14:31 ` Iain Buclaw
2015-07-24 14:37 ` Pedro Alves
2015-07-17 18:25 ` Keith Seitz
2015-07-17 18:28 ` Jan Kratochvil
2015-07-17 18:35 ` Joel Brobecker [this message]
2015-07-17 20:15 ` Simon Marchi
2015-07-17 20:57 ` Joel Brobecker
2015-07-17 21:00 ` Simon Marchi
2015-07-17 20:24 ` Sergio Durigan Junior
2015-07-20 10:06 ` Yao Qi
2015-07-21 17:11 ` 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=20150717183541.GD7406@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).