public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "myllynen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/16973] Fix lang_lib/lang_term as per ISO 639-2 Date: Tue, 01 Jul 2014 09:28:00 -0000 [thread overview] Message-ID: <bug-16973-131-li46SAeC3Z@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16973-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16973 --- Comment #3 from Marko Myllynen <myllynen at redhat dot com> --- > Marko, Do you have commit privs? If not please apply. > > I'll approve the commit privs for you. > > The patch looks good to me, once you get commit privs you can check it in. I'm about to disappear for a while due to summer holidays, perhaps you could check this one in so that it won't miss the next release? > I assume you've done a minimal build and test cycle which builds and tests > the locales? I now double checked it and noticed that km_KH needed to have lang_ab changed as well, will attach an updated patch which passes build and test cycle. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-01 9:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-21 14:00 [Bug localedata/16973] New: " myllynen at redhat dot com 2014-05-21 14:15 ` [Bug localedata/16973] " myllynen at redhat dot com 2014-05-26 12:01 ` carlos at redhat dot com 2014-06-12 19:17 ` fweimer at redhat dot com 2014-07-01 9:28 ` myllynen at redhat dot com [this message] 2014-07-01 9:30 ` myllynen at redhat dot com 2014-07-01 9:31 ` myllynen at redhat dot com 2015-08-11 7:55 ` myllynen at redhat dot com 2015-08-18 14:21 ` vapier at gentoo dot org 2015-08-18 14:21 ` cvs-commit at gcc dot gnu.org 2015-10-29 16:29 ` jsm28 at gcc dot gnu.org
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-16973-131-li46SAeC3Z@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).