public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [release/branch] Set GDB version number to 8.2.
Date: Wed, 05 Sep 2018 14:02:00 -0000	[thread overview]
Message-ID: <874lf4xctj.fsf@tromey.com> (raw)
In-Reply-To: <20180905074520.12244-1-brobecker@adacore.com> (Joel Brobecker's	message of "Wed, 5 Sep 2018 09:45:20 +0200")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> In preparation for the GDB 8.2 release, I will be pushing
Joel> this commit to the release branch.

Joel> gdb/ChangeLog:

Joel> 	* version.in: Set GDB version number to 8.2.
Joel> 	* PROBLEMS: Likewise.

Thanks, once again!, for doing the releases.

Tom

      reply	other threads:[~2018-09-05 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05  7:45 Joel Brobecker
2018-09-05 14:02 ` Tom Tromey [this message]

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=874lf4xctj.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).