public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: ktietz@sourceware.org
To: src-cvs@sourceware.org
Subject: src/libiberty ChangeLog filename_cmp.c functio ...
Date: Mon, 28 Feb 2011 18:30:00 -0000 [thread overview]
Message-ID: <20110228183014.24188.qmail@sourceware.org> (raw)
CVSROOT: /cvs/src
Module name: src
Changes by: ktietz@sourceware.org 2011-02-28 18:30:14
Modified files:
libiberty : ChangeLog filename_cmp.c functions.texi
Log message:
ChangeLog libiberty/
2011-02-28 Kai Tietz <kai.tietz@onevision.com>
* filename_cmp.c (filename_ncmp): New function.
* functions.texi: Regenerated.
ChangeLog include/
2011-02-28 Kai Tietz <kai.tietz@onevision.com>
* filenames.h (filename_ncmp): New prototype.
ChangeLog bfd/
2011-02-28 Kai Tietz <kai.tietz@onevision.com>
* archive.c (_bfd_find_nested_archive): Use filename_(n)cmp.
(adjust_relative_path): Likewise.
(_bfd_construct_extended_name_table): Likewise.
* corefile.c (generic_core_file_matches_executable_p): Likewise.
* elf32-bfin.c (bfinfdpic_relocate_section): Likewise.
* elf32-frv.c (elf32_frv_relocate_section): Likewise.
* elf32-spu.c (sort_bfds): Likewise.
(spu_elf_auto_overlay): Likewise.
* syms.c (_bfd_stab_section_find_nearest_line): Likewise.
* xcofflink.c (xcoff_set_import_path): Likewise.
* xtensa-isa.c (xtensa_regfile_lookup): Likewise.
(xtensa_regfile_lookup_shortname): Likewise.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/ChangeLog.diff?cvsroot=src&r1=1.564&r2=1.565
http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/filename_cmp.c.diff?cvsroot=src&r1=1.4&r2=1.5
http://sourceware.org/cgi-bin/cvsweb.cgi/src/libiberty/functions.texi.diff?cvsroot=src&r1=1.41&r2=1.42
next reply other threads:[~2011-02-28 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 18:30 ktietz [this message]
2014-11-05 18:23 dj
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=20110228183014.24188.qmail@sourceware.org \
--to=ktietz@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).