Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB 7.6 branch status...
Date: Tue, 19 Feb 2013 16:14:00 -0000	[thread overview]
Message-ID: <20130219161425.GD22143@adacore.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B2307B82856@IRSMSX102.ger.corp.intel.com>

> The first version that is currently on archer is functional. It needs
> some cleanup like removing the old cli and porting the tests - and it
> lacks documentation changes.
> 
> I would expect 2-3 weeks.

Given that the delay was caused by us, and that there is no big
imperative to start the release process now, we can talk about
delaying the release, but only if it makes a difference to Markus
and the users of this feature.  Some contributors have sent patches
where they said that they would not commit until the branch is cut,
and a 2-3 weeks delay is a long delay.

-- 
Joel


  reply	other threads:[~2013-02-19 16:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 22:42 Joel Brobecker
2013-02-19 12:20 ` Marcus Shawcroft
2013-02-19 15:27 ` Jan Kratochvil
2013-02-19 16:00   ` Metzger, Markus T
2013-02-19 16:14     ` Joel Brobecker [this message]
2013-02-19 17:11       ` Metzger, Markus T
2013-02-19 20:34         ` Joel Brobecker
2013-03-11  9:28           ` Metzger, Markus T
2013-03-11 10:03             ` Jan Kratochvil
2013-03-11 10:11               ` Jan Kratochvil
2013-03-11 10:13                 ` Metzger, Markus T
2013-03-11 10:11               ` Metzger, Markus T
2013-03-11 13:30             ` Joel Brobecker
2013-02-20 17:44 ` Pedro Alves
2013-02-26  3:19   ` Joel Brobecker
2013-03-10  5:04     ` Hui Zhu
2013-03-10 15:48       ` 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=20130219161425.GD22143@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=markus.t.metzger@intel.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