Currently, merge and forcemerge combine all of the tags, found versions, and fixed versions set on a bug. It has recently been brought to my attention[1] that this is probably not optimal, because most cases when merge or forcemerge is used, one bug has the right state, and the rest are dupes that do not.
To make this easier on maintainers, I'm going to change merge to require tags be equal between bugs. This also means that forcemerge will set the tags to the same value(s) as the "master bug". Secondly, I plan on combining affects between all merged sets in a forcemerge or merge, as for most of these bugs, having more affects rather than fewer is a good thing, as it reduces needless duplicates. If this is a problem or you have any objections, let me know. Don Armstrong 1: Thanks to Julien, Cyril, and Rene on IRC. -- But if, after all, we are on the wrong track, what then? Only disappointed human hopes, nothing more. And even if we perish, what will it matter in the endless cycles of eternity? -- Fridtjof Nansen _Farthest North_ p152 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120403190211.gb13...@rzlab.ucr.edu
