Re: Usability woes with Compare Revisions interface

>
> > * Refresh
>
> What would that be good for? The information doesn't change, so a
> refresh is IMHO useless.
>

Ah, now that's where our work styles differ a little bit no doubt.

Case:
I have a stable, production branch which I am comparing to trunk. The work
on trunk is comprised of multiple changesets on multiple files, so it is not
easy to patch with a .diff for each particular fix/feature.

Some of the changes take place in the same files, so just doing a diff is a
pain.

Instead, I'm simply comparing a list of files I have written down somewhere,
and as needs dictate, copying / committing them to the release branch.

So I start from a list of 200 files files with differences (Repo browser,
find branch 1, find branch 2, right click, compare revisions); and change
about 15 on production/stable branch - now I have to close my current
'compare revisions', and repeat the steps.

I may also forget to click the correct button to show differences "between
trunk and branch" vs "branch and trunk".

This is all very disruptive for the style of work I'm doing, which demands a
fair amount of concentration anyway.
Received on Tue Aug 21 02:04:12 2007