i believe you must be right regarding this program setting the modification
date of the files.
i think i will still try to change all the files in the source to a unix
style convention and then
get our developers to use the svn:eol-style property.
can you answer some questions about the property. if i set the property in
the root directory
of a working copy of the source, will it be applied to all files in the wc?
and if i then commit
the wc w/ the property applied, will it be set when other developers check
out those files?
On 9/17/07, Erik Huelsmann <firstname.lastname@example.org> wrote:
> On 9/17/07, Nathan Nobbe <email@example.com> wrote:
> > hello all,
> > im working w/ a project versioned under svn.
> > many of the files in the project have windows newline characters.
> > since we use linux as the server this is very annoying when opening the
> > files on the linux systems.
> > i have found a program to convert the windows newlines to unix newlines
> > and applied it recursively to the source. now i would like to commit
> > change,
> > however, svn does not recognize the change to the metadata as eligible
> for a
> > commit.
> > is there a way to tell svn i want to commit the changes to the file
> > metadata?
> From what you describe, I think didn't change the metadata
> (svn:eol-style) but the content of the files (CRLF->LF). Additionally,
> the tool will have reset the last-modified date on the files back to
> what it was before changing the content. Subversion uses the
> last-modified date as a means to check whether a file might have
> changed since it last updated/checkedout that file, meaning it won't
> notice the change. (In 1.5, it will start looking at the filesize
> If you want to use a mixed-eol-style environment, you should consider
> setting the svn:eol-style property on your sources to 'native'. See
Received on Mon Sep 17 16:23:23 2007