(1) you file new bug reports, you dont open old ones
(2) stop going to every open bug you see and asking for status reports. if you
want status reports, get a job as middle management where you can pester people
underneath you who have no choice but to listen.
(In reply to comment #4)
> (1) you file new bug reports, you dont open old ones
There's a benefit from reopening this one which is that the bug is already
assigned correctly and a trivial version bump is not the kind of thing that
needs to be locked away and archived. On the other hand there's a good chance
you've been using this bug tracker ten times longer than I have, so even if I
don't immediately see your point I might try not to bug you more than
necessary.
> > (2) stop going to every open bug you see and asking for status reports. if you
> want status reports, get a job as middle management where you can pester people
> underneath you who have no choice but to listen.
I did this to four bugs at once. While that might be two bugs too many, two's
still not twenty or anything. I use Gentoo/Alt - that means I have an interest
in having the ebuild in the main tree so it can be adopted, but I cannot test
any of the `unprefixed` ebuilds on my machine - a mac.
Secondly I'm not expecting anyone, especially in the case of this bug - *ED* -
to invest a lot of time or to invest any time at all into something only I
would benefit from - because that's not the case (although ed might be a bad
example for something everybody benefits from).
What I did is write a short comment. There was no swearing, no pushing, no
nothing. And if whoever gets that comment via mail has a problem with getting
that kind of *short* note - for the first time on this bug - considering it
took me longer to write than him to read, that's just ridiculous.
