public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Disabling locale at emerge output
Date: Thu, 28 Apr 2011 23:15:25 -0600	[thread overview]
Message-ID: <20110428231525.0f3f6afd@gentoo.org> (raw)
In-Reply-To: 20110428140023.246e47d7@epia.jer-c2.orkz.net

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On Thu, 28 Apr 2011 14:00:23 +0200
Jeroen Roovers <jer@gentoo.org> wrote:

> On Wed, 27 Apr 2011 21:10:55 -0600
> Ryan Hill <dirtyepic@gentoo.org> wrote:
 
> > See, you're thinking primarily in terms of bugzilla.  Like the only
> > reason someone would want to see this stuff is to paste it to a bug
> > report for a developer to look at.  I'm saying someone who doesn't
> > speak English at all (who won't be filing bugs btw) might want to be
> > able to understand the error the compiler just dumped on them without
> > needing a translator.
> 
> I countered that with the argument that if users cannot read "No such
> file or directory" then they cannot read "ERROR: app-arch/rpm-4.4.6-r7
> failed (compile phase)" either. How does that work?

Why would you need to read that?  See compiler error, portage explodes,
lots of red stars everywhere.  If I can read the compiler error I know what
happened.


-- 
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 --]

      reply	other threads:[~2011-04-29  5:10 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
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 [this message]

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=20110428231525.0f3f6afd@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