From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/15593] [PATCH] Add transliteration data for "LATIN SMALL LETTER O WITH STROKE" (ø).
Date: Wed, 09 Oct 2013 15:31:00 -0000 [thread overview]
Message-ID: <bug-15593-716-uasLv0CgYl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15593-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15593
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Toke Høiland-Jørgensen from comment #12)
> So, I tried adding it to the pending reviews wiki page, but it still won't
> let me. I'm assuming the wiki chokes on the dash in my username. I'm at a
> bit of a loss as to how to proceed to actualy get this patch merged...
Can you confirm that your login name for the wiki is `TokeHøiland-Jørgensen'?
You are the first person I've seen use UTF-8 characters in their name for a
login. I've entered in your name exactly as you specified and it should work.
Would you like to try without UTF-8 characters to see if it works then e.g.
change your login name to `TokeHoiland-Jorgensen'. If that works then we can
file a bug upstream with MoinMoin.
The next step for getting your patch checked in is to post it to
libc-alpha@sourceware.org and if you did that then post it again with the word
"Ping" added to your subject to indicate you're requesting a review for the
second time.
Please make sure you follow all the steps here:
http://sourceware.org/glibc/wiki/Contribution%20checklist
The more steps you follow the easier it is for a project member to review your
changes. The most important steps include writing up a rationale (including any
standards references) for the change and how it was tested.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-09 15:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 20:40 [Bug localedata/15593] New: " toke at toke dot dk
2013-06-06 20:40 ` [Bug localedata/15593] " toke at toke dot dk
2013-06-06 20:43 ` [Bug localedata/15593] New: " Keld Simonsen
2013-06-06 23:02 ` [Bug localedata/15593] " keld at keldix dot com
2013-06-07 13:41 ` toke at toke dot dk
2013-06-07 14:30 ` carlos at redhat dot com
2013-06-08 9:07 ` keld at keldix dot com
2013-06-08 22:25 ` carlos at redhat dot com
2013-07-23 21:23 ` toke at toke dot dk
2013-07-24 2:31 ` carlos at redhat dot com
2013-07-24 12:58 ` toke at toke dot dk
2013-07-24 22:41 ` carlos at redhat dot com
2013-07-27 12:02 ` toke at toke dot dk
2013-07-30 7:53 ` carlos at redhat dot com
2013-10-07 8:41 ` toke at toke dot dk
2013-10-09 15:31 ` carlos at redhat dot com [this message]
2013-10-16 12:05 ` toke at toke dot dk
2013-10-16 15:37 ` carlos at redhat dot com
2013-10-16 17:45 ` toke at toke dot dk
2013-10-17 1:55 ` carlos at redhat dot com
2013-10-17 8:26 ` toke at toke dot dk
2013-10-28 14:15 ` toke at toke dot dk
2013-11-24 0:54 ` toke at toke dot dk
2013-12-10 6:11 ` carlos at redhat dot com
2013-12-12 20:30 ` cjlhomeaddress at gmail dot com
2014-06-13 15:13 ` fweimer at redhat dot com
2015-05-05 9:22 ` 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-15593-716-uasLv0CgYl@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).