From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: MinGW compilation errors due to strcasecmp
Date: Sat, 19 Nov 2016 18:25:00 -0000 [thread overview]
Message-ID: <20161119182500.GC4132@adacore.com> (raw)
In-Reply-To: <837f8opj40.fsf@gnu.org>
> > You just need to go to the PR database on bugzilla:
> > - Create an account if not already done;
> > - Log in
> > - Create a PR:
> > * Subject (Eg): GDB 7.12 build failure with latest MinGW headers
> > * Body (Eg): Copy-paste the error you got
> > - Mark the PR as fixed in GDB 7.12.1:
> > * Change the target milestone to 7.12.1
> > * Change the status to fixed
> > * Add a URL to the gdb-patches discussions where the fix
> > was discussed and accepted
>
> Could this be added to the wiki in some prominent place? I need to do
> this infrequently enough that I forget what needs to be done, and
> looking through mail archives is no fun. TIA.
>
> (Btw, it seems like the wiki doesn't even have a link to bugzilla?)
Sorry for the delay. This is now done:
https://sourceware.org/gdb/wiki/PushingToReleaseBranch
There is a link to this page from the "Developing" column
in the home page ("Pushing patches to a Release Branch",
right after the link to the "Contribution Checklist").
--
Joel
next prev parent reply other threads:[~2016-11-19 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 11:20 Eli Zaretskii
2016-10-12 17:46 ` Pedro Alves
2016-10-14 7:15 ` Eli Zaretskii
2016-10-28 18:40 ` Joel Brobecker
2016-10-29 8:07 ` Eli Zaretskii
2016-10-31 12:34 ` Joel Brobecker
2016-10-31 16:40 ` Eli Zaretskii
2016-11-19 18:25 ` Joel Brobecker [this message]
2016-11-19 18:38 ` Eli Zaretskii
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=20161119182500.GC4132@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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).