First things first: I'm just a user with an interest in SVN
developments... so don't kill me if I'm wrong :P
Justin Erenkrantz wrote:
> I do wonder how this would impact TSVN or other GUI apps - how do they
> know if a directory is under version control? Does it even trigger if
> there isn't a .svn dir? Or, does it call some SVN APIs on every
> window change? I'm sure we could work with them to make sure that we
> don't screw them. I'd imagine for deep WCs, a GUI like TSVN might
> constantly be walking up the directory path to see if a .svn directory
> exists. I also don't know how well we'd handle excluded directories -
> i.e. user doesn't check in a certain sub-directory - it'd be nice to
> handle those efficiently as well without the time/walk penalties too.
> (Think of SVN's svn-test-work dirs.) Doable, but would need some
> thought, I think.
This was also what I was thinking about.
* On one hand, TSVN has always had to do some degree of crawling,
because it would also show the status of folders and mark them modified
if a file inside that folder had this status. (Or conflicted if a file
in that folder was conflicted.)
So, instead of crawling forward, it would be crawling backward, up the
tree. (Ofcouse this is much slower on network filesystems.)
*Worst case scenario* would be if you're on a slow filesystem, very deep
in a directory tree, and this tree isn't a working copy. It would have
to crawl all the way to the surface.
* On the other hand, TSVN could speed up once it knows about a SVN
working copy. Because it only has to look at one place for all working
copy information, and once it knows it's root folder there's no need for
crawling anymore (at least for certain operations).
In a worst case scenario I'd imagine TSVN should be triggered by
browsing through the root of the working copy, which would trigger TSVN
to discover a working copy, and so all subdirectories are automatically
part of the working copy.
Just 2 cents of my view ;)
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 25 22:27:21 2007