public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: vapier@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch binutils-2_24-branch updated. 5f14d9c9e3f61cb79da5e7697af2fe264def852f
Date: Tue, 07 Jan 2014 14:27:00 -0000 [thread overview]
Message-ID: <20140107142743.4972.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, binutils-2_24-branch has been updated
via 5f14d9c9e3f61cb79da5e7697af2fe264def852f (commit)
from b9c0a80c9deace8fda57ee6b558d2f73725c4823 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f14d9c9e3f61cb79da5e7697af2fe264def852f
commit 5f14d9c9e3f61cb79da5e7697af2fe264def852f
Author: Mike Frysinger <vapier@gentoo.org>
Date: Mon Jan 6 18:15:31 2014 +0000
libiberty: fix --enable-install-libiberty flag [PR 56780]
Commit 199570 fixed the --disable-install-libiberty behavior, but it also
added a bug where the enable path never works because the initial clear
of target_header_dir wasn't deleted. So we end up initializing properly
at the top only to reset it at the end all the time.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@206367 138bc75d-0d04-0410-961f-82ee72b054a4
(cherry picked from commit 369be6981b26787b2685e3b8c6da779dae8ce35f)
-----------------------------------------------------------------------
Summary of changes:
libiberty/ChangeLog | 6 ++++++
libiberty/configure | 1 -
libiberty/configure.ac | 1 -
3 files changed, 6 insertions(+), 2 deletions(-)
hooks/post-receive
--
gdb and binutils
reply other threads:[~2014-01-07 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140107142743.4972.qmail@sourceware.org \
--to=vapier@sourceware.org \
--cc=src-cvs@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).