[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Another working copy library

From: Filipe Fernandes <fernandes.fd_at_gmail.com>
Date: 2007-01-27 22:02:32 CET

Danny van Heumen wrote:
> Like Michael Sinz already said, you only have to search for 1 specific
> directory name inside every directory you crawl, so it can be done
> pretty (very) fast.

It's true... search for '.svn' towards the top and once it's found you got
your working copy. And it's likely very fast as you say, but the search would
have to be done every time, and I wonder what that would be like.

>> TortoiseSVN could add caching to remember previously found working
>> copies for faster reporting but that seems a hell of a lot dirtier
>> than simply providing a .svn directory with info as to how many levels
>> within a working copy the current folder is situated.

> It's not that big a problem I think. It's true that they would have to
> search to the top. But in case of a working copy it's sufficient to
> remember what the root is (and special cases like ignored directories
> and such).
> Once you know the location of a root of the WC it's (almost) as easy as
> comparing the start of the current WC.
> And TortoiseSVN already uses caching (TSVNCache.exe) for the current
> directories to remember modifications. So it would only take a little
> bit more information.

Very true... remembering previous WC roots would tell us quickly if the
current folder 'is' a working copy previously referenced. But in the case
where folders are opened in the course of other work being done outside of
WCs, TortoiseSVN won't have a previous record that a WC does or doesn't exist
in a path and will check all the way to root to find out that there is none.
And it must always make this check, since it can never know for sure that I
haven't simply moved a WC into the path.

You can always tell TortoiseSVN where it should and shouldn't look to minimize
the searching and in light of this fact... as I write this sentence, I guess
it won't be so bad for Tortoise. But other (future) GUI's that report as
Tortoise does will have to compensate for the lack of a .svn folder throughout
the WC in similar ways as above.

> Considering everything I think it's a small price to pay if the '.svn'
> directories are removed.
>
> Danny
>

I personally don't like the .svn folders everywhere either (I think I'd find
it massively convenient to work without them - moving/renaming files and
folders while leaving SVN to tell me what's different instead of choking on
misplaced .svn folders). But I worry about the future of GUI's like Tortoise
having constantly to search to the top just to know what it might be looking at.

filipe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 27 22:03:17 2007

This is an archived mail posted to the Subversion Dev mailing list.