From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <xdje42@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB 7.9 branching - 2 weeks to go (Mon, Jan 12th)!
Date: Mon, 05 Jan 2015 04:17:00 -0000 [thread overview]
Message-ID: <20150105041744.GF5445@adacore.com> (raw)
In-Reply-To: <CAP9bCMToKK0PAHSKA4aL5uqeb7LGnYjszN46LXvoOhqg60LB0Q@mail.gmail.com>
> > One more week to go, if we still maintain the original target date...
>
> Dang. For some reason I had the 19th stuck in my mind.
> I owe a few people some reviews.
Depending on the patches, we might be able to branch while accepting
they be ported to the branch. If too complex, however, then we can
also delay the creation of the branch, if we feel it would make sense
to do so.
--
Joel
next prev parent reply other threads:[~2015-01-05 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 7:15 Joel Brobecker
2014-12-30 15:42 ` Eli Zaretskii
2014-12-30 15:51 ` Joel Brobecker
2014-12-31 18:11 ` Jan Kratochvil
2015-01-05 4:10 ` Joel Brobecker
2015-01-05 4:13 ` Doug Evans
2015-01-05 4:17 ` Joel Brobecker [this message]
2015-01-05 16:07 ` Eli Zaretskii
2015-01-06 16:09 ` Steve Ellcey
2015-01-06 16:38 ` 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=20150105041744.GF5445@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).