public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jan Kundrat (jkt)" <jkt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/en: bugzilla-howto.xml
Date: Thu, 05 Mar 2009 12:13:21 +0000	[thread overview]
Message-ID: <E1LfCS1-0004sM-1Z@stork.gentoo.org> (raw)

jkt         09/03/05 12:13:21

  Modified:             bugzilla-howto.xml
  Log:
  #260477, encourage LC_ALL=C when reporting bugs

Revision  Changes    Path
1.16                 xml/htdocs/doc/en/bugzilla-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.15&r2=1.16

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- bugzilla-howto.xml	5 Mar 2009 12:02:04 -0000	1.15
+++ bugzilla-howto.xml	5 Mar 2009 12:13:20 -0000	1.16
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.15 2009/03/05 12:02:04 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.16 2009/03/05 12:13:20 jkt Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,7 +20,7 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.13</version>
+<version>1.14</version>
 <date>2009-03-05</date>
 
 <chapter>
@@ -492,6 +492,23 @@
 </p>
 
 <p>
+Please make sure you always include error messages in English, even when your
+system language is set to something else. You can temporarily switch to English
+locale by prepending <c>LC_ALL=C</c> to the emerge command like this:
+</p>
+
+<pre caption="Temporarily switching locale to English">
+# <i>LC_ALL=C emerge sys-apps/foobar2</i>
+</pre>
+
+<note>
+This is also about the only time you should use the <c>LC_ALL</c> environmental
+variable for specifying locale settings. If you are looking for a way to switch
+your system's language, then please consult our <uri
+link="guide-localization.xml">Localization Guide</uri> instead.
+</note>
+
+<p>
 Make errors are the actual error and the information the developer needs. When
 you see "make: ***", this is often where the error has occurred. Normally, you
 can copy and paste 10 lines above it and the developer will be able to address






             reply	other threads:[~2009-03-05 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 12:13 Jan Kundrat (jkt) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 12:01 [gentoo-commits] gentoo commit in xml/htdocs/doc/en: bugzilla-howto.xml Sven Vermeulen (swift)
2010-02-28  6:14 Joshua Saddler (nightmorph)
2009-03-05 12:02 Jan Kundrat (jkt)
2009-01-26  7:34 Joshua Saddler (nightmorph)
2008-05-23 20:42 Sven Vermeulen (swift)
2008-02-01 19:30 Jan Kundrat (jkt)
2008-01-31 14:31 Jan Kundrat (jkt)

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=E1LfCS1-0004sM-1Z@stork.gentoo.org \
    --to=jkt@gentoo.org \
    --cc=gentoo-commits@lists.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