Re: Bugs again

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



Jan de Groot schrieb:

The only valid reason I see for closing a bug as upstream, is when
upstream made a decision in the software which is reported as bug by the
user. An example of this is excluding evince from the menus by using
NoDisplay=True in the .desktop file. This bug is opened now and then,
and it's either closed as duplicate of the previous one, or it's closed
as upstream. Upstream decided to remove it from the menus because it's a
viewer application that can't do anything else than file->open, so let
them handle the bugreports for that.

I am always tempted to close nvidia bugs as "upstream", as we can do nothing about them and there is no public bugtracker I know of. But you are right, most of the time we should at least track the bugs even if the are upstream.

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux