public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Pedro Alves <palves@redhat.com>,
	Luis Machado <lgustavo@codesourcery.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Define an error function in the PPC simulator library.
Date: Tue, 05 Sep 2017 19:38:00 -0000	[thread overview]
Message-ID: <20170905193820.fc7lsuzmjbifovyo@adacore.com> (raw)
In-Reply-To: <22805795-41a7-9f1d-7237-d537b6d12c81@FreeBSD.org>

> >> Will do.  Is there still time to merge this into 8.0.1 
> > 
> > I think the plan was yesterday, but it didn't happen yet, so I think
> > there's still time, though likely not much.

That's correct, because there were some tickets pending, so I said
I'd give extra time.

I'm reviewing the situation every couple of days, with the next
update being tomorrow.

> The bug is closed and has the 8.0.1 milestone.  Thanks!

Perfect. I was a bit worried when I saw the commits get in without
the PR number in the ChangeLog.

If the PR has the 8.0.1 milestone, then no need to worry about
listing them explicitly in the wiki. That's what the list to bugzilla
is there for.

-- 
Joel

      reply	other threads:[~2017-09-05 19:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 16:34 John Baldwin
2017-04-13 13:25 ` Luis Machado
2017-04-14 18:02   ` John Baldwin
2017-05-05 19:51     ` John Baldwin
2017-05-19 16:28       ` [PING] " John Baldwin
2017-06-06 17:49         ` John Baldwin
2017-06-23  6:39           ` Sebastian Huber
2017-09-04 14:19     ` Pedro Alves
2017-09-05  3:00       ` John Baldwin
2017-09-05  9:14         ` Pedro Alves
2017-09-05 11:46           ` John Baldwin
2017-09-05 19:38             ` Joel Brobecker [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=20170905193820.fc7lsuzmjbifovyo@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    --cc=lgustavo@codesourcery.com \
    --cc=palves@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).