severity 970210 important thanks Don Armstrong pisze: > > retitle 970210 repeatmerged=no can't be configured to show a bug other than > the lowest numbered bug > severity 970210 wishlist
It's not a wishlist, it's a bug, as the current behavior, that is based on some strange assumption that a report filled first is always better than a report filled later, is just against the common sense. I know that the things have like this for ages, and everybody got used to it, and got used to having to work-around it by changing the title of merged reports, but still I consider this as a bug. > > The documentation is pretty clear: "Forcibly merges two or more bug > reports. The settings of the first bug listed which must be equal in a > normal merge are assigned to the bugs listed next. IMHO nothing here says which bug will be displayed as the "main" bug. > > It doesn't cause a bug to be listed when repeatmerged=no, change the > title, or anything like that. Bug report is not only about settings and title, but also its contents... For example if one bug report contains only information that something does not work, but the other bug report provides also some analysis or work-around, than it is obvious to me which of them we should prefer. And similarly in the ispell case, https://bugs.debian.org/979575 provides more information than your arbitrarily chosen https://bugs.debian.org/979549 . > > Hope that clarifies things a bit. And I hope I convinced you to actually fix this bug. Regards, robert
