From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: et_EE locale and language of error messages
Date: Fri, 19 May 2006 16:01:21 +0000 (UTC) [thread overview]
Message-ID: <e4kq4h$qpg$1@sea.gmane.org> (raw)
In-Reply-To: e4kgai$j3n$1@sea.gmane.org
Stefan Schweizer <genstef@gentoo.org> posted e4kgai$j3n$1@sea.gmane.org,
excerpted below, on Fri, 19 May 2006 15:13:48 +0200:
> Marc Hildebrand wrote:
>> Otoh LC_ALL=C could help if you intend to use a .utf-8 locale as root,
>> though. So if it does help solving bugs and causes no trouble, why not.
>
>
> ok, we have prepared a patch now, so everyone can have a look at it.
> http://dev.gentoo.org/~zmedico/tmp/portage_lc_all.patch
>
> the default LC_ALL=C will be overwriteable by PORTAGE_LC_ALL= in
> make.conf. Of course broken settings like et_EE will not be supported.
>
> If no other objections come up against patch will be added to portage
> within a day. So, if you have any problem with it, speak up now.
While I cautiously support the idea, limiting objections to a day appears
to be ramming something thru, and beyond that, simply isn't practical for
a number of folks who may have either valid objections or valid
suggestions that could ease potential future issues. This is
/particularly/ the case when some may be ignoring the list ATM due to the
thread getting the most activity ATM. If folks aren't interested in that,
they may be avoiding the list ATM as a simple matter of efficiency and
personal sanity.
Also, it's Friday. What about those that have taken off for a long
weekend?
Please... Tuesday at the very earliest seems reasonable, and I'd suggest
an entire week from first post, so next Friday. Also note that portage is
in 2.1-rc freeze ATM, and while this might be considered a bug-fix
exception, /some/ sort of debate, more than a day, seems warranted.
Otherwise, 2.2 would look like a more reasonable target.
Again, this is from someone that otherwise favors the idea. A day's
debate is simply not enough, and looks like you are just trying to ram it
thru without /letting/ there be debate. Please reconsider at least on the
timing.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-19 16:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 9:38 [gentoo-dev] et_EE locale and language of error messages Stefan Schweizer
2006-05-19 10:22 ` Marc Hildebrand
2006-05-19 13:13 ` [gentoo-dev] " Stefan Schweizer
2006-05-19 13:30 ` Harald van Dijk
2006-05-19 16:01 ` Duncan [this message]
2006-05-19 17:14 ` Marius Mauch
2006-05-19 17:27 ` [gentoo-dev] " Stefan Schweizer
2006-05-19 18:10 ` Marius Mauch
2006-05-19 17:45 ` [gentoo-dev] " Zac Medico
2006-05-22 16:57 ` Wiktor Wandachowicz
2006-05-19 12:49 ` [gentoo-dev] " Harald van Dijk
2006-05-19 13:02 ` Jakub Moc
2006-05-19 13:09 ` Patrick McLean
2006-05-19 13:24 ` Harald van Dijk
2006-05-19 13:55 ` Carsten Lohrke
2006-05-19 13:44 ` Daniel Drake
2006-05-19 13:40 ` Harald van Dijk
2006-05-19 15:44 ` [gentoo-dev] " Stefan Schweizer
2006-05-19 16:05 ` Harald van Dijk
2006-05-24 0:59 ` [gentoo-dev] " Mike Frysinger
2006-05-24 10:36 ` Kevin F. Quinn
2006-05-24 11:17 ` Harald van Dijk
2006-05-24 12:58 ` Kevin F. Quinn
2006-05-24 11:42 ` Jakub Moc
2006-05-24 13:12 ` Kevin F. Quinn
2006-05-25 21:09 ` Mike Frysinger
2006-05-26 7:37 ` Mike Frysinger
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='e4kq4h$qpg$1@sea.gmane.org' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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