On 2010-04-24, Kai Willadsen <[email protected]> wrote: >> On a related topic (I think), is there anyway to avoid the complete >> re-scan after reverting or commiting a single file? It really mucks >> up workflow if after every operation you have to wait a minute or two >> for meld to rescan a large progje tree for no reason. > > Not currently, no. Meld is overly conservative, and assumes that it > needs to rescan the tree after any VC operation.
Are there cases where commiting or reverting file X changes the status of a file other than X? > There is the start of some refresh-related code in VcView, but > judging by some FIXMEs and the lack of VC-specific information, it's > a fair way from functional. OK, I guess meld just isn't work for that use case: reviewing each of a set of changed file and then commiting or reverting the file. -- Grant _______________________________________________ meld-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/meld-list
