public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/11484] new Bulgarian locale
Date: Wed, 11 May 2011 04:54:00 -0000	[thread overview]
Message-ID: <bug-11484-716-UNbX5JReGo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11484-716@http.sourceware.org/bugzilla/>

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

--- Comment #12 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-05-10 22:53:43 UTC ---
(In reply to comment #11)
> +%EY (year+era)         2010 сл.н.е.

And there is already a problem.  You're completely overdoing it.  Eras are
pretty much only for Japan and nothing else.


There are drastic changes.  I understand you cannot get the previous maintainer
to comment.  But I need assurance.  Did you announce the availability of the
locale, have people test it, and report back?  I have nothing else to get by.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-05-11  4:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11484-716@http.sourceware.org/bugzilla/>
2011-05-10  5:03 ` drepper.fsp at gmail dot com
2011-05-10 21:42 ` bugtrack at roumenpetrov dot info
2011-05-10 21:42 ` bugtrack at roumenpetrov dot info
2011-05-11  4:54 ` drepper.fsp at gmail dot com [this message]
2011-05-11  4:54 ` bugtrack at roumenpetrov dot info
2011-05-13 20:05 ` bugtrack at roumenpetrov dot info
2011-05-13 20:05 ` bugtrack at roumenpetrov dot info
2011-05-13 20:06 ` bugtrack at roumenpetrov dot info
2011-05-13 20:06 ` bugtrack at roumenpetrov dot info
2011-05-13 20:06 ` bugtrack at roumenpetrov dot info
2011-05-13 20:06 ` bugtrack at roumenpetrov dot info
2011-05-13 20:15 ` bugtrack at roumenpetrov dot info
2011-11-11  6:36 ` bugtrack at roumenpetrov dot info
2012-04-06 21:10 ` bugtrack at roumenpetrov dot info
2012-04-06 21:12 ` bugtrack at roumenpetrov dot info
2012-04-06 23:25 ` bugtrack at roumenpetrov dot info
2012-04-07  6:24 ` cjlhomeaddress at gmail dot com
2012-04-13 19:26 ` pasky at ucw dot cz
2012-04-14 11:54 ` bugtrack at roumenpetrov dot info
2012-12-01 16:26 ` bugtrack at roumenpetrov dot info
2013-11-04 20:46 ` bugtrack at roumenpetrov dot info
2014-06-30 19:07 ` fweimer at redhat dot com
2016-02-19 10:47 ` [Bug localedata/11484] bg_BG: updated locale vapier at gentoo dot org
2016-04-22  4:39 ` vapier at gentoo dot org
2017-10-21  8:26 ` maiku.fabian at gmail dot com
2010-04-09 19:59 [Bug localedata/11484] New: new Bulgarian locale bugtrack at roumenpetrov dot info
2010-04-09 20:04 ` [Bug localedata/11484] " bugtrack at roumenpetrov dot info
2010-04-11  4:21 ` drepper at redhat dot com
     [not found] ` <20100411042138.19257.qmail@sourceware.org>
2010-04-13 19:46   ` Roumen Petrov
2010-04-21 21:29 ` pasky at suse dot cz
2010-04-21 22:50 ` bugtrack at roumenpetrov dot info
2010-04-22  5:12 ` pasky at suse dot cz
2010-04-22 21:25 ` bugtrack at roumenpetrov dot info
2010-06-01  2:47 ` pasky at suse dot cz
2010-06-01  2:48 ` pasky at suse dot cz

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=bug-11484-716-UNbX5JReGo@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@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).