From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>, Binutils <binutils@sourceware.org>
Subject: Re: ANNOUNCEMENT: we have now switched to new git hooks (was: "Re: RFC: using AdaCore's git hooks for binutils-gdb.git ...")
Date: Mon, 12 Jan 2015 04:58:00 -0000 [thread overview]
Message-ID: <20150112045849.GW5445@adacore.com> (raw)
In-Reply-To: <CAMe9rOp2GGp6e-i38N-hBdOeuc-SMx5rsAE2wGxCL9W5y6p9mw@mail.gmail.com>
> This checkin:
>
> https://sourceware.org/ml/binutils-cvs/2015-01/msg00074.html
>
> didn't update the bugzilla.
OK - I think I found the source of the problem (configuration issue),
and I suspect that only binutils was affected (ie, GDB PRs would have
been updated).
It should be fixed, now, but we should keep our eyes peeled for
the next commit with a PR number, for both binutils and GDB, just
to be sure.
--
Joel
next prev parent reply other threads:[~2015-01-12 4:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 13:58 RFC: using AdaCore's git hooks for binutils-gdb.git Joel Brobecker
2014-11-28 14:08 ` H.J. Lu
2014-11-28 14:27 ` Joel Brobecker
2014-11-28 14:42 ` Joel Brobecker
2014-11-28 18:06 ` Joseph Myers
2014-11-28 20:50 ` Sergio Durigan Junior
2014-11-29 2:53 ` Joel Brobecker
2014-12-01 11:34 ` Pedro Alves
2014-12-07 14:21 ` Joel Brobecker
2014-12-08 6:05 ` Sergio Durigan Junior
2014-12-13 16:51 ` Joel Brobecker
2014-12-14 20:47 ` Joel Brobecker
2014-12-21 22:46 ` Joel Brobecker
2015-01-05 4:13 ` Joel Brobecker
2015-01-10 6:59 ` ANNOUNCEMENT: we have now switched to new git hooks (was: "Re: RFC: using AdaCore's git hooks for binutils-gdb.git ...") Joel Brobecker
2015-01-11 16:21 ` H.J. Lu
2015-01-12 4:08 ` Joel Brobecker
2015-01-12 4:16 ` Joel Brobecker
2015-01-12 18:03 ` Cary Coutant
2015-01-12 4:58 ` Joel Brobecker [this message]
2015-01-12 5:05 ` H.J. Lu
2015-01-12 6: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=20150112045849.GW5445@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@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).