From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Unbreak DJGPP port of GDB
Date: Thu, 04 Jun 2015 02:41:00 -0000 [thread overview]
Message-ID: <83fv68qjon.fsf@gnu.org> (raw)
In-Reply-To: <20150603220141.GE2801@adacore.com>
> Date: Wed, 3 Jun 2015 15:01:41 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org
>
> Regardless, the procedure when pushing changes to the branch after
> a release has been made is to update the wiki:
>
> https://sourceware.org/gdb/wiki/GDB_7.9_Release
>
> (which means you need a PR number as well).
That's a nuisance.
next prev parent reply other threads:[~2015-06-04 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 15:19 Eli Zaretskii
2015-05-28 8:47 ` Yao Qi
2015-05-28 14:42 ` Eli Zaretskii
2015-05-30 10:11 ` Eli Zaretskii
2015-06-03 22:01 ` Joel Brobecker
2015-06-04 2:41 ` Eli Zaretskii [this message]
2015-06-04 4:08 ` Joel Brobecker
2015-06-04 14:57 ` Eli Zaretskii
2015-06-09 18:36 ` Joel Brobecker
2015-06-09 18:50 ` Eli Zaretskii
2015-06-09 18:56 ` 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=83fv68qjon.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@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).