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

RE: [PMX:SPAM8%] RE: RE: Re: Visual Studio.Net and Subversion - Will this make it into a release?

From: Demyanovich, Craig - Apogent <cdemyanovich_at_apogent.com>
Date: 2004-03-08 17:52:23 CET

My original reply follows the quote. I mistakenly sent it to the original
poster instead of to the list. Sorry.

> > I'm still a newbie, but does it have to be even that complicated?
> > How about:
> >
> > // svn_wc.h
> > #ifdef WIN32
> > #define SVN_WC_ADM_DIR_NAME "svn";
> > #else
> > #define SVN_WC_ADM_DIR_NAME ".svn";
> > #endif
> >
> > The folder is flagged as 'hidden' on my system by default, so that
> > should meet the "hidden folder" design. If the period starting the
> > folder name is
> > the true problem, doesn't this solve it?
> >
> I think the problem people have with this is that you can't
> pick up the wc and move it somewhere else without having a
> modified svn program on that system. For example, you can't
> move a Windows wc to Linux.

I haven't had a chance to use Subversion yet. However, while using CVS, the
thought of moving a working copy from one machine (A) to another (B) has
never even occurred to me. Rather, I would commit from (A) anything worth
keeping, and check it out to (B). You could always label the version as
some kind of migration. The feature that says I should be able to move a
working copy from one machine to another is a very, very low-priority one
for me. It just doesn't feel like proper use of

Craig Demyanovich

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 8 17:53:20 2004

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