[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#133578: gdm bug #133578. Intend to NMU.



Hamish Moffatt <hamish@debian.org> wrote:

> On Fri, Apr 23, 2004 at 11:32:36AM +0200, Mathieu Roy wrote:
>> The question must be something like:
>> 
>>     Can the maintainer refuse to apply this patch that fix a problem
>>     while it does not break anything and would greatly enhance the
>>     software for non-english speakers?
>
> Could you please phrase the question in a less "loaded" way ie one that
> doesn't indicate your opinion of the issue? Simply
>
>      Can the maintainer refuse to apply this patch?
>
> would do it.

Hum, I think important to mention that

     - it does not break anything 
     - it is important for non-english speakers.

If it sound "loaded", it is maybe just because of the nature of the
patch, not specifically because of my own point of view. Anyway,
I'm not a sophist, so my point of view is related to the nature of the
patch.

But, indeed, I'm sure it is possible to come up with a less harsh
sentence.  

>> The problem at stakes here is not really whether gdm should handle
>> i18n via /etc/environment. The problem is about a maintainer that
>> refuse to take care of many users needs (yes, i18n is not a minor part
>> of a GNU/Linux system) and refuse to apply harmless workarounds. 
>                                              ^^^^^^^^^^^^^^^^^^^^
>
> And that's the source of the disagreement.

Well, I did not read anything in the whole thread that contradict that
point. But maybe I just missed it. If so, can you please give me an
hint?


Regards,

-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+



Reply to: