public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eddy dot petrisor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug localedata/2125] localedata has problems for ro_RO
Date: Tue, 02 May 2006 06:38:00 -0000	[thread overview]
Message-ID: <20060502063854.26891.qmail@sourceware.org> (raw)
In-Reply-To: <20060109102645.2125.eddy.petrisor@gmail.com>


------- Additional Comments From eddy dot petrisor at gmail dot com  2006-05-02 06:38 -------
(In reply to comment #18)
> I added the locale changes.  But it seems you never relaly tested it.

I have been running those changes for almost two months now, so I wouldn't say I
never really tested them.

>  The
> lang_term and lang_lib fields were missing.

I am really sorry; it appears that I converted an older version of the files
used to create a patch when I was trying not to use patches (as you requested).

I will check again to see if nothing else was lost.

Could you be more clear, have you added lang_term and lang_lib?

FWIW, the file split attachements were consistent wit each other (the fields in
question were not mentioned in the changelog); Thanks for noticing!

> The ISO 4217 data has already been updated.

I don't know who did this, but in Debian this change was made some time before
the actual new locale enetered. Maybe Denis Barbier pushed it here.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2125

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-05-02  6:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 10:26 [Bug localedata/2125] New: " eddy dot petrisor at gmail dot com
2006-01-09 10:28 ` [Bug localedata/2125] " eddy dot petrisor at gmail dot com
2006-02-21 13:08 ` eddy dot petrisor at gmail dot com
2006-02-22  8:01 ` eddy dot petrisor at gmail dot com
2006-02-24 14:17 ` eddy dot petrisor at gmail dot com
2006-02-24 14:20 ` eddy dot petrisor at gmail dot com
2006-02-24 14:22 ` eddy dot petrisor at gmail dot com
2006-02-24 14:24 ` eddy dot petrisor at gmail dot com
2006-03-08 14:13 ` tgakic at chem dot tue dot nl
2006-03-19 23:48 ` eddy dot petrisor at gmail dot com
2006-04-24  6:11 ` drepper at redhat dot com
2006-04-25  8:11 ` eddy dot petrisor at gmail dot com
2006-04-25 17:11 ` drepper at redhat dot com
2006-04-25 18:41 ` eddy dot petrisor at gmail dot com
2006-04-26 21:37 ` eddy dot petrisor at gmail dot com
2006-04-26 21:39 ` eddy dot petrisor at gmail dot com
2006-04-26 21:40 ` eddy dot petrisor at gmail dot com
2006-04-26 21:42 ` eddy dot petrisor at gmail dot com
2006-05-01 19:01 ` drepper at redhat dot com
2006-05-02  6:38 ` eddy dot petrisor at gmail dot com [this message]
2006-05-03 19:09 ` eddy dot petrisor at gmail dot com
2006-05-03 19:28 ` eddy dot petrisor at gmail dot com
2006-05-03 19:30 ` eddy dot petrisor at gmail dot com
2006-06-09  6:56 ` eddy dot petrisor at gmail dot com
2006-06-09  6:56 ` eddy dot petrisor at gmail dot com
2006-06-09  7:27 ` eddy dot petrisor at gmail dot com
2006-08-03 18:38 ` drepper at redhat dot com
2006-08-04 10:06 ` eddy dot petrisor at gmail dot com

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=20060502063854.26891.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).