From: Joel Brobecker <brobecker@adacore.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Release 2.24
Date: Sat, 07 Dec 2013 03:37:00 -0000 [thread overview]
Message-ID: <20131207033711.GH3175@adacore.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1312062350040.19368@tp.orcam.me.uk>
[I removed binutils]
> I have committed the change now, thanks for your help with getting it
> done. You have previously requested a small description of the change for
> the purpose of making a release announcement -- please let me know if the
> commit message is enough for your needs or whether you'd prefer something
> more elaborate.
For one item, I could do it myself. But generally speaking, it helps me
if the committer also adds an entry in the GDB release wiki page:
https://sourceware.org/gdb/wiki/GDB_7.6_Release
You'll need a PR first, and then a reference to that PR in the wiki
page. I know it's a bit of a pain, but it saves me a ton of time
during the minor releases, because I can just copy/paste the page
and put it in the announcement. Before we started doing that, I was
going through the entire list of commits, trying to write a small
description of the effect of each commit. Some times, I wasn't quite
sure whether my description was completely accurate... With this system,
it's fast for me, and accurate for the users.
The good news is, once we have the entry, I think I can produce
the release Mon or Tue.
Thank you,
--
Joel
next prev parent reply other threads:[~2013-12-07 3:37 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
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 [this message]
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=20131207033711.GH3175@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.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