Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: GDB 7.7 branching on Monday?
Date: Thu, 19 Dec 2013 18:22:00 -0000	[thread overview]
Message-ID: <20131219182206.GI3493@adacore.com> (raw)
In-Reply-To: <CAMe9rOp0M_8WAMyviNJ4X_xr7tA1GKGCQ-7yaQ=5Z5xdxGZ5TQ@mail.gmail.com>

> I have 4 patches I like to see in GDB 7.7:
> 
> https://sourceware.org/ml/gdb-patches/2013-12/msg00309.html
> https://sourceware.org/ml/gdb-patches/2013-12/msg00307.html
> https://sourceware.org/ml/gdb-patches/2013-12/msg00313.html
> https://sourceware.org/ml/gdb-patches/2013-12/msg00310.html

I'll need a little more from you.  What's your estimate for getting them
in, and what are the consequences of not having them for 7.7?

Here is what I propose: We go ahead with the branch on Monday.
Looking at the patches, they seem to be relatively simple enough
that they should be good candidates for backporting to the branch
if they get approved after Monday.

-- 
Joel


  reply	other threads:[~2013-12-19 18:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 17:59 Joel Brobecker
2013-12-19 18:06 ` H.J. Lu
2013-12-19 18:22   ` Joel Brobecker [this message]
2013-12-19 18:27     ` H.J. Lu
2013-12-19 21:52   ` Mark Kettenis
2013-12-19 22:29     ` H.J. Lu
2013-12-19 20:31 ` Sergio Durigan Junior
2013-12-20  3:28   ` Joel Brobecker
2013-12-20  3:37     ` Sergio Durigan Junior
2013-12-25  4:48     ` Sergio Durigan Junior
2013-12-28  3:11       ` Joel Brobecker
2013-12-23  8:01 ` Joel Brobecker
2014-01-07  2:54   ` Joel Brobecker
2014-01-07 23:44     ` Pierre Muller
2013-12-24 21:22 Nick Bull
2013-12-25  2:47 ` 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=20131219182206.GI3493@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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