Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,
	       Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Subject: Re: heads up: GDB 7.7 official release Wed Jan 29th (tomorrow)
Date: Tue, 28 Jan 2014 04:02:00 -0000	[thread overview]
Message-ID: <m3txcooisy.fsf@redhat.com> (raw)
In-Reply-To: <20140128023118.GC4101@adacore.com> (Joel Brobecker's message of	"Tue, 28 Jan 2014 06:31:18 +0400")

On Tuesday, January 28 2014, Joel Brobecker wrote:

> I really was planning on sending this email at the end of last
> week, and then forgot. It's been a fairly quiet 3 weeks since
> the first pre-release, and there are no longer any known failures
> mentioned in the release wiki page, so I am planning on making
> the official release tomorrow. Please shout if there is something
> I missed :).

Heya!

This is definitely not a blocker, but I'd like to know what are the
status of the patches submitted by Edjunior for PPC64.  There is at
least one of them which solves a false-positive, so for the sake of
avoiding wasting time if someone finds these "failures" in the future,
it might be good to check those in.

Thanks,

-- 
Sergio


  reply	other threads:[~2014-01-28  4:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  2:31 Joel Brobecker
2014-01-28  4:02 ` Sergio Durigan Junior [this message]
2014-01-28 14:59   ` Joel Brobecker
2014-01-28 17:49 ` Ulrich Weigand
2014-01-28 18:07   ` Joel Brobecker
2014-01-28 18:22     ` Ulrich Weigand
2014-01-29  8:14       ` Joel Brobecker
2014-01-29  9:31         ` Mark Kettenis
2014-01-29 18:57           ` Ulrich Weigand
2014-01-29 11:05 Tobias Burnus

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=m3txcooisy.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=emachado@linux.vnet.ibm.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