Re: [ jEdit-devel ] svn:eol-style = native (LF vs CRLF)

[Kazutoshi S. <k_s...@f2...>]

Alan Ezust wrote:
 > I did some googling to better understand it and came across this thread:
 > http://www.mail-archive.com/har...@in.../msg13473.html
 >
 > Is it necessary to impose such a policy among all committers of the
 > jedit project?

Yes. Manual settings on each committer's machine is one of the best
practices. Unfortunately, it can't be per project. It is per machine.
So we can't enforce the settings.

 > If so, should we point them to the apache svn config
 > file, since it is probably going to be similar for committers of
 > project jedit?

It looks quite well defined one. But since it is a setting per machine,
having a reduced set for project jedit in the own repository might be
preferable.


More aggressive approach is, setting pre-commit hook script which
checks the property of adding files and rejects a commit which doesn't
match a policy. In this way, the policy is applied per repository.

I found that SourceForge.net have fine supports of hook scripts. They
provide some common hooks, and check-mime-type.pl is a similar
function.
   https://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#scripts
So submitting a new Feature Request might be appropriate. One assumed
issue is that checking eol-style requires a configuration like the
auto-prop setting.

--
k_satoda