public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch master updated. f0c897ef0a1aa2c4983cd216a4aadff82dcbad4a
Date: Thu, 21 Nov 2013 17:50:00 -0000	[thread overview]
Message-ID: <20131121175036.21196.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, master has been updated
       via  f0c897ef0a1aa2c4983cd216a4aadff82dcbad4a (commit)
      from  8d5c4b7bfdfa5f2b40fa056132823c8e9497dc72 (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=f0c897ef0a1aa2c4983cd216a4aadff82dcbad4a

commit f0c897ef0a1aa2c4983cd216a4aadff82dcbad4a
Author: schwab <schwab@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Fri Nov 15 17:49:36 2013 +0000

    config/ * picflag.m4 (m68k-*-*): Use default PIC flag.
    
    gcc/
    * configure: Regenerate.
    
    libada/
    * configure: Regenerate.
    
    libgcc/
    * configure: Regenerate.
    
    libiberty/
    * configure: Regenerate.
    
    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@204854 138bc75d-0d04-0410-961f-82ee72b054a4

-----------------------------------------------------------------------

Summary of changes:
 config/ChangeLog    |    4 ++++
 config/picflag.m4   |    3 ---
 libiberty/ChangeLog |    4 ++++
 libiberty/configure |    3 ---
 4 files changed, 8 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
gdb and binutils


                 reply	other threads:[~2013-11-21 17:50 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=20131121175036.21196.qmail@sourceware.org \
    --to=tromey@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).