Re: Invalid file type management

I was wrong. And I don't see my previous post to tack it onto, so
I'll add new message here. I said it was the backspace in the
comment, well it isn't -- the user had a bad habit in CVS of including
the log info into the file and then committing that back in again, so
the backspace is in the beginning of the file, thus it is being
considered a binary file, even when I explicitly set mime type, etc.
So, I can fix it from here on, but would add my vote to having a way
to allow smartsvn to consider the backspace a "non-binary"; character.

Messages in this topic (4) Reply (via web post) | Start a new topic

.

Hello Gary,

> So, I can fix it from here on, but would add my vote to having a way
> to allow smartsvn to consider the backspace a "non-binary"; character.

SVN probably detects this file correctly as text file (you can try manually
copying the file to have it duplicated as unversioned, adding the file and
checking the Type column resp. Properties|Edit MIME Type).

In this case, we already have a request on our RFE list to consider this SVN
MIME Type for the File Compare resp. Change Report.

--
Best regards,
Marc Strapetz
_____________
SyntEvo GmbH
www.syntevo.com

&quot;rgbeckmann" < gary.beckmann%40integra-ls.com">gary.beckmannintegra-ls.com> wrote:

> I was wrong. And I don't see my previous post to tack it onto, so
> I'll add new message here. I said it was the backspace in the
> comment, well it isn't -- the user had a bad habit in CVS of including
> the log info into the file and then committing that back in again, so
> the backspace is in the beginning of the file, thus it is being
&gt; considered a binary file, even when I explicitly set mime type, etc.
> So, I can fix it from here on, but would add my vote to having a way
> to allow smartsvn to consider the backspace a "non-binary"; character.
>
>
>
>
> Yahoo! Groups Links
&gt;
>
>
>
>

Messages in this topic (5) Reply (via web post) | Start a new topic

.