Re: keywords migration

It's ok.

Thanks.

Julien

2010/11/5 Michael Haggerty <[email protected]>

> On 11/04/2010 05:16 PM, Julien HEYMAN wrote:
> > I try to migrate cvs to svn.
> > I used cvs version 1.12.13 and svn version 1.6.12
> > I used cvs2svn 2.3.0.
> > config.py is the origin file, i don't edit it (I don't edit nothing)
> >
> > I have in my cvs repository a file toto.txt with keywords $Date$. The
> > date as updated automatically after each commit.
> >
> > I run cvs2svn but when I look the file, the keyword is not migrated.
> > I check it with : svnlook proplist /tmp/test /trunk/projet/toto.txt, but
> > nothing is set.
> >
> > my command line : ./cvs2svn  -vv -s /tmp/test /work/cvs
> >
> > I join my file.
> >
> > So why the cvs2svn don't set svn:keywords propertie on my file ?
>
> Sorry, this is a documentation bug.  Since version 2.0, files are
> treated as binary by default unless a --default-eol option is used.
> That means that by default files do not get a svn:eol-style property and
> (as a consequence of this) do not get an svn:keywords property.
>
> If you think you have been consistent in marking binary files as such in
> CVS, then you can use something like "--default-eol=native" to treat all
> non-binary CVS files as text files with the specified EOL style, and
> then cvs2svn will also attach an svn:keywords property to such files.
>
> This whole EOL handling / mime types / keyword expansion system in
> cvs2svn is very confusing and I am (slowly) working to make it more
> transparent.  For now, just remember that it is almost always necessary
> to use the --default-eol option to get useful results.
>
> Michael
>
> --
> Michael Haggerty
> [email protected]
> http://softwareswirl.blogspot.com/
>

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

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