> From: Rusty Koonce
> -- Can you setup specific files/directories/repositories for
> use with a
> lock-modify-unlock check-out scheme?
As Ben Collins-Sussman said in a previous reply this is a post 1.0 feature.
Until then I find svn's behavior with opaque binary files to be usable. If
the svn:mime-type is set to something non text, svn does not attempt a
merge. Updates of non text files svn create two files in your working copy;
one with you local changes and one from the current repository tree. After
an update I run a search script to find replaced files, then choose which
one to discard.
> My current employer uses VSS (I know!). Management often
> sees things a
> little differently than developers; as such, a VSS database
> converter and a
> GUI have very high priority with them as well.
If you are developing on windows, TortiseSVN (tortoisesvn.tigris.org) and
TortiseCVS are the slickest GUI interfaces to source code control systems I
have ever seen.
On this list there was recently a discussion about writing a SCC API
provider for svn. Since the SCC API is what VSS speaks, if you get yourself
on the svn SCC API provider mail list you can probably find people who are
concerned with VSS->svn conversion. Perhaps somebody will hack the VSS to
cvs conversion script (vss2cvs.pl) to work import to svn. vss2cvs.pl was
recently posted on the gnu cvs info mail list
http://mail.gnu.org/mailman/listinfo/info-cvs . Has anybody on this list
tried a two stage conversion from vss?
cvs -d /tmp/cvs/repo
vss2cvs.pl /tmp/cvs/repo /vss/repo
svnadmin create /new/svn/repo
cvs2svn.py -s /new/svn/repo /tmp/cvs/repo
Received on Fri Jan 16 19:49:17 2004