Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When using the "Review Changes" feature of the version control interface, if an existing status document is available, it should be reused and refreshed instead of a new one being opened.
If you commit frequently from inside MD and use a keyboard shortcut for the Review Changes view, you can end up opening dozens of these windows over the span of a hack session.
On the other hand, it is useful to be able to see changes from different directories in different views.
Agreed—I should have clarified that before: it would reuse existing windows /on the same scope/.
I generally review changes on the solution scope by hitting my keyboard shortcut, which gives me (over time) many windows named 'src+'. My proposal is to reuse only these, and reuse Review Changes windows on smaller scopes for the appropriate scope.
Fixed in tip of master. ;D