Re: (maybe)bug report & issues

Hi Michael
 
>> [keyword expansion problem]
> If you have binary files in your repository that might accidentally
> contain strings like "$Id$", then making the change that you suggest
> will cause those strings to be expanded too, corrupting the file.
>
> The default cvs2svn options are chosen to minimize the chance of
> accidental file corruption, even for people who haven't marked their
> binary files as binary in CVS. If you are diligent about such things,
> then you can probably fix most of these problems by using
> "--default-eol=native".

I do understand this text/binary issue. The problem is, that adding '--default-eol=native' does not change anything regarding to my problem. In file 'cvs2svn_lib/dvcs_common.py' at line 105 the keyword strategie is set to 'collapsed':

KeywordHandlingPropertySetter('collapsed')

I did not find any code that would change this default to 'expanded' (for non-binary files). Is this not possible using commandline? Do i have to use an option file to achieve this?

>> [Date format problem]
> You seem to be using an old version of CVS, and so the CVS date
> expansion is in the old style. If somebody would check out your CVS
> repository using a newer version of CVS, they would get the new-style
> expansion.

I think the situation is a bit different: I am currently using a cvs version '1.12.13-MirDebian-8' to perform my checks with 'cvs2git'. A cvs checkout using this version still get's the old style date. So i assume that the date format is set during the commit (which have all been made with a 1.11 version) and cvs does not do any formatting during checkout.

Anyway, thank your for your hint.

regards
Henning

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3054773

To unsubscribe from this discussion, e-mail: [[email protected]].