When it comes to "merge commits" where bug tags would be hidden from the mainline (if the revision "node" isn't "expanded").
I suggest that the all bug --fixes that occurred in "sub" revisions be shown next to the particular revision shown in the mainline (the revision where the branch was merged and committed ).
So just by looking at the mainline the user can see all the fixes that took place without clicking or expanding revisions etc. Also once the "merged committed" revision is expanded then those bug tags can then be shown alongside the "more" correct revision where the bug was actually fixed...
When it comes to "merge commits" where bug tags would be hidden from the mainline (if the revision "node" isn't "expanded").
I suggest that the all bug --fixes that occurred in "sub" revisions be shown next to the particular revision shown in the mainline (the revision where the branch was merged and committed ).
So just by looking at the mainline the user can see all the fixes that took place without clicking or expanding revisions etc. Also once the "merged committed" revision is expanded then those bug tags can then be shown alongside the "more" correct revision where the bug was actually fixed...
ie:
Mainline fully "collapsed":
r101 bug #1234 bug #222 bug#33
|
r100
|
r99
now expand revision r101:
r101
\
r100.3 bug #1234
|
r100.2 bug #222
|
r100.1 bug #33
/
r100
|
r99
Not sure if I'm making sense here :)