On 03/08/2012 16:18, hasufell wrote:
> So that would simply mean we add that information to the devmanual?
>
> Should I open a bug with a devmanual patch then?
Please do. QA will back the request for verbose logs by default.
--
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/01/2012 06:07 PM, Michał Górny wrote:
> On Wed, 01 Aug 2012 13:13:43 +0200 hasufell
> wrote:
>
>> We already had a discussion about cmake-utils.eclass and forcing
>> verbose build log for that which was approved:
>> http://archives.gentoo.org
On 03/08/2012 09:54, Alexis Ballier wrote:
> I don't think anyone will object to enforcing a given locale to be
> present, even en_US.UTF-8; people will object if they have to use that
> locale.
>
> Maybe locale-gen can even generate it on-the-fly in $T, I don't know.
Agreed. And there _is_ a way
On Fri, 3 Aug 2012 17:47:24 +0200
Michał Górny wrote:
> > Python upstream is doing what they think is best in using unicode.
> >
> > That said, what if we just temporarily set a locale in the ebuild
> > for running tests and elsewhere? Is this unreasonable or
> > impossible? It might not be a gre
On Fri, 3 Aug 2012 09:59:42 -0500
Matthew Summers wrote:
> On Thu, Aug 2, 2012 at 1:32 PM, Mike Gilbert
> wrote:
> > On Thu, Aug 2, 2012 at 2:21 PM, Diego Elio Pettenò
> > wrote:
> >> On 01/08/2012 23:42, Fabian Groffen wrote:
> >>> Honestly, if some asian person has whatever charset that I oft
On Thu, Aug 2, 2012 at 1:32 PM, Mike Gilbert wrote:
> On Thu, Aug 2, 2012 at 2:21 PM, Diego Elio Pettenò
> wrote:
>> On 01/08/2012 23:42, Fabian Groffen wrote:
>>> Honestly, if some asian person has whatever charset that I often find in
>>> spam messages, but is not UTF-8, are you then going to t
