On Fri, 20 Jul 2007, Oleg Verych wrote: > When i looking trough say 1024 messages in bug-dist, all i have are > lines with author, subject, data. The Subject have bug number and > what was set in it by author. Sometimes wordings there are not > attractive without context. And the big one will be the package name > there. E.g. i don't care for "Subject: Bug#OMEGA patch" for ncurses, > but care for SLang, etc.
If you don't care about specific packages, then you don't want to read -dist; you want to subscribe to the PTS for those specific packages (or otherwise filter -dist appropriately.) > Again, this is optimization thing, not necessarily suitable for > skilled developers with bts tool and by-package MLs with less > traffic. But i've found more efficient to check one place for bugs > reports. Other on-topic MLs are for discussions like this one. I'm still not certain what your use case is; if you're looking for information on a specific package, bugs.debian.org is the place to look. If you want to know about a certain error string, bugs.debian.org/cgi-bin/search.cgi is far more accurate than google or gmane. If you just want to see the bugs scroll by, then that's about what -dist is useful for... but then you have to filter it out yourself if you want it filtered. > Also reducing size of header "X-Debian...: pkgname" to just pkgname > in Subject is a little size optimization. Size optimization isn't the point; the point is utility. It's much easier to filter based on discrete headers than Subject:, especially when Subject: foo pkg breaks bar pkg makes things even more useless. > One more thing about size, if you permit. Why empty headers are > added? It's a waste IMHO. What empty headers? Don Armstrong -- I may not have gone where I intended to go, but I think I have ended up where I needed to be. -- Douglas Adams _The Long Dark Tea-Time of the Soul_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
