From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/19247] pap_CW: update glibc locale file
Date: Fri, 22 Apr 2016 04:57:00 -0000 [thread overview]
Message-ID: <bug-19247-716-zI5Lfu0G8Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19247-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19247
Mike Frysinger <vapier at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #3 from Mike Frysinger <vapier at gentoo dot org> ---
this locale file looks significantly different from the one that's in current
git. when you write a file like this and change just about everything, it
makes it extremely difficult for us to review & merge.
can you instead do:
- grab latest file from git:
https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/pap_CW;hb=HEAD
- change *only* the fields that you want to update
- make *no* other changes to whitespace, comments, etc...
then upload that file here for us to look at.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-04-22 4:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 12:29 [Bug localedata/19247] New: Update pap_CW " manuel at enkidu dot coop
2015-11-15 21:18 ` [Bug localedata/19247] pap_CW: update " vapier at gentoo dot org
2015-11-15 22:55 ` manuel at enkidu dot coop
2016-04-22 4:57 ` vapier at gentoo dot org [this message]
2017-10-21 6:44 ` maiku.fabian at gmail dot com
2024-01-15 10:33 ` maiku.fabian 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=bug-19247-716-zI5Lfu0G8Z@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).