MessageWell, it may not seem like a problem if you compare a single file that
you know has no differences, but imagine you’re checking a specific directory
with hundreds of files, only one or two of which have changed. Fossil will
invoke WinDiff and have you look at every single file in that directory,
instead of the one or two that actually have changed. So, it IS kind of a
problem, unless you avoid using WinDiff and use –tk option.
From: dave
Sent: Thursday, September 25, 2014 12:07 AM
To: 'Fossil SCM user's discussion'
Subject: Re: [fossil-users] gdiff/opendiff on os x: suppress unchanged files?
Oh, OK. Well, if I do, say
C:\Experiments\libfossil>fossil gdiff configure
in my environment, I do indeed get a WinDiff on that file showing no changes,
but isnt' that what I asked it to do, rather than not pop up WinDiff at all and
make me think something is wrong?
Oh, well, I guess I don't understand the particualr use-case, and probably I'm
just adding noise to the conversation at this point, so I'll duck out. At
least in the scenarios I described below, it seems to be working right to my
sensibilities in at least version 1.29.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
