From: Joel Brobecker <brobecker@adacore.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Tristan Gingold <gingold@adacore.com>,
Richard Sandiford <rdsandiford@googlemail.com>,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Release 2.24
Date: Mon, 18 Nov 2013 17:25:00 -0000 [thread overview]
Message-ID: <20131118172117.GD3481@adacore.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1311181646080.21686@tp.orcam.me.uk>
> I see 2.24 is about to roll out, so I'll try to find some time this week
> to make the necessary adjustments for a matching GDB 7.6.2 maintenance
> release -- assuming as per your recent statement, that making 7.7 can take
> a while yet.
What are your parameters? I've started working on the scripts this
weekend, and unfortunately for me, I am bursting with ideas of things
to try out - this is going to be helpful for the future, but not so
good for the present. I am planning on working on it an hour every day,
so I should have branching hopefully done soon, and then at least
pre-release creation done right after that.
To explain a bit the delay, the switch to git is more than just
changing some configuration-management commands in the script.
Git opens up the door for doing things a little differently.
For instance, I will have the scripts sends the email for me,
instead of me doing some tedious copy/pasting - this is now possible
because I don't have to be afraid of losing the connection to
sourceware while creating the branch from a repo on my laptop.
Same thing for GPG signing.
If the delay is unbearable to your platform, then we'll need to
temporary re-open the CVS, and produce an extra release from there.
Or the alternative is to produce a release by hand, but that would
take much more time, I think. Neither of these 2 options are
attractive, so it'd be better if we could wait for me to be ready.
--
Joel
next prev parent reply other threads:[~2013-11-18 17:21 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
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 [this message]
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=20131118172117.GD3481@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=macro@codesourcery.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