On Mon, Feb 9, 2009 at 17:44, Mark Phippard <markphip_at_gmail.com> wrote:
> On Mon, Feb 9, 2009 at 11:41 AM, jcompagner <jcompagner_at_gmail.com> wrote:
> > ahh ok
> > Refresh revision info doesnt really say to me that it will get merge
> > information. What does it exactly refresh besides merge? Also the commit
> > comment and so on (because most stuff is static/fixed right?)
> We had already added this option because it is possible for things
> like the comment to have been edited and we are working exclusively
> off the local cache for this information. So we updated the option to
> also retrieve the merge information at the same time.
the more i think about it and look how this behavior works (if i refresh
file X and i see the right line
and then i go to file Y that was also in that merge i see there the line
then i think for us if i just could say where to get the merge info from it
would be just 2 queries per project and
you had it for all the files in 1 project that i want.
For example we have
/trunk/j2db and /branch/4x/j2db
and those 2 folders contain all the merge properties for every file they
So wouldnt it just be enough to just query the merge properties for those 2
locations and then for every file i open thats inside that project you know
> > Multi select a few revision and then tell it to refresh would be nice
> > i dont have to have it for everything.
> File an issue. I think when we first added this you could not
> multi-select in the graph at all. You can do that now though, so this
> option could possibly be supported.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2009-02-11 00:22:51 CET