Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Tristan Gingold <gingold@adacore.com>,
	Joel Brobecker	<brobecker@adacore.com>
Cc: Richard Sandiford <rdsandiford@googlemail.com>,
	<binutils@sourceware.org>,	<gdb-patches@sourceware.org>
Subject: Re: Release 2.24
Date: Wed, 18 Sep 2013 20:56:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1309182134580.4379@tp.orcam.me.uk> (raw)
In-Reply-To: <BB32BE2A-A3CC-494C-9FB2-CFD322F49EA3@adacore.com>

On Wed, 18 Sep 2013, Tristan Gingold wrote:

> > for the binutils 2.24 release, I plan to create the branch in Septembre, but I'd like
> > to wait for the git transition to create the release.
> > 
> > If you plan to submit big patches or if you want to submit a patch for the release,
> > do not hesitate to speak.
> 
> I have just created the binutils-2_24-branch.

 Just as a reminder, can we please coordinate so that GDB 7.7 is released 
before binutils 2.24?

 On the MIPS target we've switched PLT formats produced by LD for MIPS16 
and microMIPS binaries and for correct frame unwinding GDB has to 
understand them.  Otherwise it'll fail in odd ways, e.g. when stepping 
over a function called via PLT.  Of course all code required is there in 
our shared repository, it's just a matter of making the releases in the 
right order so that ordinary developers have a version of GDB to upgrade 
to available if needed.

 Thanks,

  Maciej


       reply	other threads:[~2013-09-18 20:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com>
     [not found] ` <BB32BE2A-A3CC-494C-9FB2-CFD322F49EA3@adacore.com>
2013-09-18 20:56   ` Maciej W. Rozycki [this message]
2013-09-18 21:32     ` Joel Brobecker
2013-09-18 22:26       ` Maciej W. Rozycki
2013-09-19 12:20         ` Joel Brobecker
2013-11-18 16:58         ` Maciej W. Rozycki
2013-11-18 17:25           ` Joel Brobecker
2013-11-21 19:33             ` Maciej W. Rozycki
2013-11-22  3:02               ` Joel Brobecker
2013-11-22  3:28                 ` H.J. Lu
2013-11-22  4:22                   ` Joel Brobecker
2013-11-23 19:12                   ` Hans-Peter Nilsson
2013-11-22  8:17                 ` Joel Brobecker
2013-11-22 15:01                 ` Tom Tromey
2013-11-24 10:07                   ` Joel Brobecker
2013-11-25  9:49               ` Tristan Gingold
2013-11-25  9:52                 ` Joel Brobecker
2013-11-25 12:19                   ` Maciej W. Rozycki
2013-11-25 12:56                     ` Joel Brobecker
2013-12-02 16:21                       ` Maciej W. Rozycki
2013-12-02 19:51                         ` Richard Sandiford
2013-12-03  2:52                           ` Joel Brobecker
2013-12-06 23:55                             ` Maciej W. Rozycki
2013-12-07  3:37                               ` Joel Brobecker
2013-12-08  3:56                                 ` Joel Brobecker
2013-12-08  8:40                                   ` Joel Brobecker
2013-09-19  3:59       ` Jeff Law
2013-09-20 13:15         ` Michael Matz

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=alpine.DEB.1.10.1309182134580.4379@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=rdsandiford@googlemail.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