Re: Source control: Scanning for changes

[Edwin Vane <revane gmail com>]

On Thu, Jul 16, 2009 at 9:34 AM, Vincent Legoll<vincent legoll gmail com> wrote:
> On Thu, Jul 16, 2009 at 3:15 PM, Edwin Vane<revane gmail com> wrote:
>>> I don't understand this one, meld generally parses the vc status command
>>> output to detect file states.
>>
>> As Vincent just mentioned, meld seems to recursively go through the
>> entire directory tree looking for changes. I'm guessing it's just
>> calling the source control's 'status' command in each directory.
>> However, with large directory structures this can take a long time. I
>> sometimes have a non-versioned subtree within the directory structure
>> (created as part of the build) and searching these things is really
>> unnecessary. In my experience with svn and mercurial, just calling the
>> 'st' command in the root directory automatically shows all changes in
>> subdirectories. In theory, meld can just use this list instead of
>> recursively traversing the directory structure looking for changes.
>
> I think some VC plugins do it this way, but not all of them

I'm not surprised. I would suggest then that for VC plugins that do
show all changes recursively that meld take advantage of that. In
other cases, there's not a whole lot one can do except maybe prune
directories that are not under VC.

-- 
Edwin V