public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>,
	Pedro Alves <palves@redhat.com>,
	Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: One month away from GDB 8.0 branching
Date: Thu, 16 Feb 2017 09:05:00 -0000	[thread overview]
Message-ID: <20170216090505.jood7ctopopt57qm@adacore.com> (raw)
In-Reply-To: <wwok1suz7zm4.fsf@ericsson.com>

> I created a PR for this issue :
> https://sourceware.org/bugzilla/show_bug.cgi?id=21169
> 
> I've marked it Target Milestone 8.0

Thanks. And thanks for mentioning that this is indeed a regression;
this helps confirm that this is indeed blocking for 8.0.

> But the wiki doesn't work for me, I was sure I had an account but can't
> login, invalid l/p, and I can't create an account I get : 
> 503 You triggered the wiki's surge protection , on my first try....
> 
> If someone would kindly add it to the maybe for release section it would
> be nice.

Do you have reasons to believe that we should not be creating
the branch until this is fixed? If yes, then I'll add it to
the wiki, no problem. If we can create the branch, and fix the
issue on the branch later on, then adding it to the wiki is
unnecessary (the wiki is only for those who prefer that option
over creating a PR).

Thanks!
-- 
Joel

  reply	other threads:[~2017-02-16  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  3:59 Joel Brobecker
2017-02-16  0:23 ` Antoine Tremblay
2017-02-16  9:05   ` Joel Brobecker [this message]
2017-02-16 12:42     ` Antoine Tremblay
2017-02-16 22:28   ` Yao Qi
2017-02-17 10:12     ` Joel Brobecker
2017-02-17 12:38       ` Antoine Tremblay
2017-02-19 13:48         ` Joel Brobecker
2017-02-19 19:43           ` Antoine Tremblay
2017-02-17 12:50     ` Antoine Tremblay
2017-02-19 13:53       ` Joel Brobecker
2017-02-19 19:50         ` Antoine Tremblay

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=20170216090505.jood7ctopopt57qm@adacore.com \
    --to=brobecker@adacore.com \
    --cc=antoine.tremblay@ericsson.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tom@tromey.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).