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

Re: Question about propset

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-08-22 17:36:39 CEST

cmpilato@collab.net writes:

> (trying to keep this dialogue on the public list so other brains can assist)
> "Drew Jetter" <ajetter1@cox.net> writes:
> > Thanks for your help. If windows doesn't have wildcard support,
> > that's okay, because I can use a similar fix to the one Roman
> > suggested...but what do I do when subversion incorrectly thinks
> > that a file is a text file during an import? It doesn't seem like there
> > is any way to tell it that any files are binary until after the import
> > is finished. Once the import is finished, the file is already screwed
> > up. So even if you set it to binary at that point, it can't fix it because
> > the first copy of the file in the repository is screwed up. Now if
> > there is something I can do about this, let me know. If I'm just
> > asking for a feature that hasn't been added yet....then maybe I'll go
> > ahead and try modifying the source myself, cuz I really need this
> > in order to use subversion. Thanks again for helping me...
> Hm...I'm really confused as to how the files are getting "screwed up"
> just by importing them. I was under the impression that Subversion
> didn't tweak file bits unless keyword expansion or newline conversion
> was explicitly enabled...perhaps there is a real bug here. Please
> give more details here.

Yes, the Subversion repository and network layer treat *all* data as
binary data. The concept of "textness vs binariness" is something
only understood by the working copy, and is controlled by setting the
svn:mime-type property. (If the working copy thinks something is a
text file, then it will attempt to do contextual merging during
updates, and possibly insert conflict markers.)

If 'svn import' incorrectly guesses at the text/binariness, this
shouldn't be a big deal at all. Just check out a working copy, fix
the properties by hand, and recommit. The data won't change one whit
in the repository.

Are you actually seeing data corruption somewhere? Or are you just
*assuming* that things are corrupted, having been scarred by cvs's
"-kb" flags in the past? :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 17:38:52 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.