On Sun, 23 Dec 2007, Brice Goglin wrote:
> Santiago Vila wrote:
> > No, it's not fine to close a bug without doing anything at all to fix it.
> > It's the duty of the maintainer to reproduce the bug,
> >
>
> You are not going to tell me what I need to do. I am not paid to do this, I
> try to d
Santiago Vila wrote:
No, it's not fine to close a bug without doing anything at all to fix it.
It's the duty of the maintainer to reproduce the bug,
You are not going to tell me what I need to do. I am not paid to do
this, I try to do my best in my free time and I have several hundreds of
On Sun, 23 Dec 2007, Julien Cristau wrote:
> On Sun, Dec 23, 2007 at 13:47:44 +0100, Santiago Vila wrote:
>
> > No, it's not fine to close a bug without doing anything at all to fix it.
>
> If you're the only one who reproduces this and cares about it, and you
> don't reply to queries about the b
On Sun, Dec 23, 2007 at 14:44:56 +0100, Julien Cristau wrote:
> On Sun, Dec 23, 2007 at 13:47:44 +0100, Santiago Vila wrote:
>
> > No, it's not fine to close a bug without doing anything at all to fix it.
> >
> If you're the only one who reproduces this and cares about it, and you
> don't reply
On Sun, Dec 23, 2007 at 13:47:44 +0100, Santiago Vila wrote:
> No, it's not fine to close a bug without doing anything at all to fix it.
>
If you're the only one who reproduces this and cares about it, and you
don't reply to queries about the bug's status, then it's perfectly fine
to close it imo
On Sat, 22 Dec 2007, Brice Goglin wrote:
> Santiago Vila wrote:
> > Last time I checked (etch) the bug was still there.
> >
> > The fact that I didn't have a system running lenny to check this bug
> > does not make the bug to disappear. So please don't close bugs
> > gratuitously.
>
> The fact
tags 145797 +moreinfo etch
thank you
Santiago Vila wrote:
Last time I checked (etch) the bug was still there.
The fact that I didn't have a system running lenny to check this bug
does not make the bug to disappear. So please don't close bugs
gratuitously.
The fact that you never replier t
reopen 145797
thanks
Last time I checked (etch) the bug was still there.
The fact that I didn't have a system running lenny to check this bug
does not make the bug to disappear.
So please don't close bugs gratuitously. At the very minimum, you should
try to reproduce the bug yourself (which is
reassign 145797 xserver-xorg-input-kbd
kthxbye
On Sat, May 4, 2002 at 17:55:21 +0200, Santiago Vila wrote:
> The X server seems to modify the keyboard repeat settings normally set
> in the BIOS, which I normally set as 250ms before starting to repeat
> and 30 chars per second when repeating. As
9 matches
Mail list logo
