kicad-developers team mailing list archive

[Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>]

On Sun, May 12, 2013 at 09:08:49PM -0500, Dick Hollenbeck wrote:
> Until I recommitted all text files, I was having problems with false diffs.  This is the
> reason for the *rules_check* repo.  To show that that repo works.  If the test passes, I
> can do a similar commit for testing to cross the bridge once and for all.
> 
> Unfortunately the attached "rules" file would have no effect it if only existed in the
> repo.  You have to copy it where bazaar wants it, although we should put it into the repo
> for ease of standardization across all developer's systems.  Bazaar developers have
> alluded to a possible future where one in the repo will be effective.

That's the same approach I used to try to fix. I agree with the false
diff issue. However once everything is 'right' in the repo it should
work.

Why the bzr people did implement it as a postprocess step???
svn:eol-style works *way* better, too bad...

The thing I didn't check is what happen when a win user does a commit.
I hope it does the right thing (i.e. switch the CRLF to whatever the
repo is configured to hold), otherwise it's useless.

-- 
Lorenzo Marcantonio
Logos Srl