From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Disabling locale at emerge output
Date: Wed, 27 Apr 2011 02:47:46 -0600 [thread overview]
Message-ID: <20110427024746.57ff61e5@gentoo.org> (raw)
In-Reply-To: 20110426060237.237a2397@epia.jer-c2.orkz.net
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
On Tue, 26 Apr 2011 06:02:37 +0200
Jeroen Roovers <jer@gentoo.org> wrote:
> On Mon, 25 Apr 2011 20:05:03 -0600
> Ryan Hill <dirtyepic@gentoo.org> wrote:
>
> > You want to force English on all our users because you can't be
> > bothered to ask a reporter to repost an error message using LC_ALL=C?
>
> Are you saying you are setting up the tree-wide project that
> automatically translates LC_MESSAGES? Round of applause!
Nope, but I am raising donations to fund an instructive manual on the usage
of the NEEDINFO resolution.
> > For a growing portion of our user base it's not "nice" to see these
> > messages in their native language, it's fucking "necessary".
>
> Another round of applause for the appalling attitude.
>
> Could you elaborate on the need to read error messages in your own
> language? How is the sys-apps/portage translation project doing anyway?
> Still only in Polish, hm? :)
Que? Are you saying that because portage is in English that people that
don't speak English don't use Gentoo? I would have to disagree.
If you think that getting the occasional bug report in a language you aren't
familiar with is annoying, imagine how not being able to get any build output
you can read might feel, especially if the reason is only because some dev
couldn't be bothered to occasionally ask someone to repost an error message in
English.
This reminds me of the time someone wanted to ban inline `emerge --info`
postings in bugzilla (ie. attachments only) because they found scrolling
through them bothersome.
In other words, suck it up.
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-27 8:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 11:31 [gentoo-dev] Disabling locale at emerge output Tomáš Chvátal
2011-04-22 12:31 ` ragavender rao
2011-04-22 17:53 ` Andreas K. Huettel
2011-04-24 16:48 ` Jeroen Roovers
2011-04-24 21:55 ` [gentoo-dev] " Duncan
2011-04-25 1:57 ` Jeroen Roovers
2011-04-25 5:24 ` Duncan
2011-04-25 4:05 ` Serkan Kaba
2011-04-25 6:14 ` Ulrich Mueller
2011-04-25 10:24 ` Jeroen Roovers
2011-04-25 13:40 ` ragavender rao
2011-04-22 12:37 ` [gentoo-dev] " Fabian Groffen
2011-04-22 12:57 ` Chí-Thanh Christopher Nguyễn
2011-04-26 2:06 ` [gentoo-dev] " Ryan Hill
2011-04-22 15:23 ` [gentoo-dev] " Jeroen Roovers
2011-04-22 17:50 ` Andreas K. Huettel
2011-04-22 15:40 ` Jeremy Olexa
2011-04-24 21:27 ` Andreas K. Huettel
2011-04-26 2:05 ` [gentoo-dev] " Ryan Hill
2011-04-26 4:02 ` Jeroen Roovers
2011-04-26 6:35 ` Michał Górny
2011-04-27 8:47 ` Ryan Hill [this message]
2011-04-27 16:26 ` Jeroen Roovers
2011-04-27 22:09 ` Chí-Thanh Christopher Nguyễn
2011-04-27 22:14 ` ross smith
2011-04-28 3:10 ` Ryan Hill
2011-04-28 12:00 ` Jeroen Roovers
2011-04-29 5:15 ` Ryan Hill
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=20110427024746.57ff61e5@gentoo.org \
--to=dirtyepic@gentoo.org \
--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