roccomoretti at hotpop.com
Mon Oct 13 15:53:21 CEST 2003
Sorry for brining up old news, but my Netscape e-mail wasn't letting me
log in for more than about 2 seconds ... so I changed free email
providers. I've had a backlog of messages to work through ...
>>I'm still a bit worried that if fixeol actually changes content, as would be
>>the case if it is run by someone on another platform than the one used to
>>create it, then svn will record it as completely changed (ideal source for
>>conflicts). The only solution I could imagine would be to make sure that
>>people specify files to be text when they first add it to the repository.
>>Somehow the default "files-are-binary" of SVN creates different, new kind of
>>problems than the default "files-are-text" of CVS. Maybe a no-default
>>you-must-specify-it-explicitely wouldn't have been such a bad idea.
>we could enforce this on a pre-commit hook and maybe other things
>like e.g. that REST-files compile without errors. The latter would make
>a checkin of documents slower but i think it's worth it IMO.
One option would be to sell our friends at subversion on the concept of
repository level tagging. I would imagine that it is common to want
*all* *.py, *.txt, *.c and *.h files to be handled as eol-native files
throughout the repository.
One way repository level tagging could work is that on the svn server is
a config file that applies globally to all files and directories in the
repository, setting specific property tags upon file/directory addition.
svn:eol-style = native
would cause any text or python files to have the svn:eol-style property
be set to native. Though generally applied, it could apply to all tags
and file designations.
PyPy svn admins: Does this seem like a reasonable feature to request? Or
is it already availible?
More information about the Pypy-dev