Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: binutils@sourceware.org, gdb@sourceware.org
Cc: drow@false.org, gcc@gcc.gnu.org, ian@airs.com
Subject: PATCH: Update src/intl from gcc/intl
Date: Fri, 19 May 2006 15:57:00 -0000	[thread overview]
Message-ID: <200605191537.IAA07067@hpsje.cup.hp.com> (raw)

OK, Here is an official patch proposal to replace the contents of the
src/intl tree with the bits from gcc/intl.

I tested the change on HPPA and IA64 HP-UX and on IA64 Linux.  The Linux
build didn't prove much because it used the system gettext bits but the
HP-UX builds built and used the new intl directory with no problems and
I am willing to try and fix any problems caused by the change if other
platforms have problems with it.


2006-05-19  Steve Ellcey  <sje@cup.hp.com>

	* MAINTAINERS: Change intl updating instructions.
	* config.rpath: Copy from GCC tree.
	* intl: Replace contents of intl directory with intl from GCC tree.


*** MAINTAINERS.orig	Wed May 17 11:58:10 2006
--- MAINTAINERS	Wed May 17 12:01:37 2006
*************** gdb/; readline/; sim/; GDB's part of inc
*** 47,61 ****
  include/
  	See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
  
! libiberty/; libiberty's part of include/ 
  	gcc: http://gcc.gnu.org
  	Changes need to be done in tandem with the official GCC
  	sources or submitted to the master file maintainer and brought
! 	in via a merge.  Note: approved patches in gcc's libiberty
! 	are automatically approved in this libiberty also; feel free
! 	to merge them yourself if needed sooner than the next merge.
! 	Otherwise, changes are automatically merged, usually within
! 	a day.
  
  ltconfig; ltmain.sh; ltcf-*.sh
  	libtool: http://www.gnu.org/software/libtool/
--- 47,61 ----
  include/
  	See binutils/, gdb/, sid/, gcc/, libiberty/ etc.
  
! intl/; config.rhost; libiberty/; libiberty's part of include/ 
  	gcc: http://gcc.gnu.org
  	Changes need to be done in tandem with the official GCC
  	sources or submitted to the master file maintainer and brought
! 	in via a merge.  Note: approved patches in gcc's libiberty or
! 	intl are automatically approved in this libiberty and intl also;
! 	feel free to merge them yourself if needed sooner than the next
! 	merge.  Otherwise, changes are automatically merged, usually
! 	within a day.
  
  ltconfig; ltmain.sh; ltcf-*.sh
  	libtool: http://www.gnu.org/software/libtool/
*************** winsup/
*** 99,105 ****
  	See also winsup/MAINTAINERS.
  
  config-ml.in; makefile.vms; mkdep; setup.com;
! etc/; intl/; utils/;
  	Any global maintainer can approve changes to these
  	files and directories.
  
--- 99,105 ----
  	See also winsup/MAINTAINERS.
  
  config-ml.in; makefile.vms; mkdep; setup.com;
! etc/; utils/;
  	Any global maintainer can approve changes to these
  	files and directories.
  


             reply	other threads:[~2006-05-19 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 15:57 Steve Ellcey [this message]
2006-05-19 16:30 ` Nick Clifton
2006-05-19 17:17   ` Daniel Jacobowitz
2006-05-19 17:57 ` DJ Delorie
2006-05-19 21:16   ` Steve Ellcey
2006-05-19 21:16     ` DJ Delorie
2006-05-21 14:14       ` Mark Mitchell
2006-05-22 22:37         ` DJ Delorie
2006-05-22 17:59       ` Steve Ellcey
2006-05-23  1:14         ` DJ Delorie

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=200605191537.IAA07067@hpsje.cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=binutils@sourceware.org \
    --cc=drow@false.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=ian@airs.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