[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fix libunistring in MS-Windows locales
From: |
Karl Berry |
Subject: |
Re: Fix libunistring in MS-Windows locales |
Date: |
Sun, 6 Jul 2014 23:57:06 GMT |
You didn't volunteer for libiconv- and gettext-related modules
so I reverted their maintainer to 'all';
Daiki has been the maintainer of gettext (the package) for quite some
time, as you know. I asked him about libiconv (the package) in other
email; I'm guessing he'll reply after the weekend, hopefully with an
"ok" :).
However, what is the benefit to labelling individuals as maintainers of
modules in the first place, rather than just having everything be "all"?
Was it that Bruno wanted to personally approve changes to "his" modules?
I seem to remember proposing (years ago) to automatically sync gnulib
from gettext (the source repository or release, as preferred), and
Bruno did not want to do anything like that, but wanted to do everything
by hand. I never understood, though it seemed to all magically work out.
I guess we should figure out how the gnulib updates of this stuff are
going to work in the post-Bruno world.
karl
Re: Fix libunistring in MS-Windows locales, Eli Zaretskii, 2014/07/15
- Re: Fix libunistring in MS-Windows locales, Paul Eggert, 2014/07/15
- Re: Fix libunistring in MS-Windows locales, Eli Zaretskii, 2014/07/15
- Re: Fix libunistring in MS-Windows locales, Daiki Ueno, 2014/07/16
- Re: Fix libunistring in MS-Windows locales, Eli Zaretskii, 2014/07/16
- Re: Fix libunistring in MS-Windows locales, Daiki Ueno, 2014/07/17
- Re: Fix libunistring in MS-Windows locales, Eli Zaretskii, 2014/07/17
- Re: Fix libunistring in MS-Windows locales, Paul Eggert, 2014/07/17
- Re: Fix libunistring in MS-Windows locales, Daiki Ueno, 2014/07/17