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

Re: Visual Studio.Net and Subversion - Will this make it into a release?

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-03-09 01:55:44 CET

On Monday 08 March 2004 11:36, Arild Fines wrote:
> Craig L. Ching wrote:
> >> 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.
>
> How many people actually *need* that? Isn't half the point of using a vcs
> in the first place to get away from having to "share" source trees between
> different environments/users?
>
> If I were working on a project in both unix and windows(which I am, to some
> degree), I'd rather have a separate working copy for each environment.

FWIW, I use this feature *every* day. I'm currently developing solutions
under both Linux and Windows, and I've got my working copy on a Samba share.
I love the fact that I only need to maintain 1 working copy.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 9 01:58:18 2004

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