kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

Gang,

Please put the attached file into your BZR_HOME directory and name it rules.

This file is also now in the root of the source tree, but has no effect there.  It
contains instructions as comments that relate to linux and windows.  Mac users will have
to confirm on your own where BZR_HOME is.   Likely this is ~/.bazaar directory like on linux.

On any of the platforms, *you must copy rules file to proper directory* for bazaar to put
it into play.

All text files in the repo now have LF line endings.  To preserve this, we all have to
have a rules file like this one in play.  If <BZR_HOME>/rules is in play, then on your
next check out or branch, you will get native line endings on all text files in your
working tree, while the repo stays with LF line endings.


Thanks,

Dick

# This is the Bazaar "rules" file for KiCad Developers.
# http://doc.bazaar.canonical.com/beta/en/user-reference/eol-help.html

# To put it into use, you must _copy_ it to your BZR_HOME directory, where BZR_HOME
# varies by platform.  In that target directory, described in more detail below,
# simply make sure this file has the name "rules", but without quotes.

# platform   BZR_RULES dir and rules filename
#---------   --------------------------------
# linux      ~/.bazaar/rules
# WinXP      C:\Documents and Settings\<username>\Application Data\Bazaar\2.0\rules
# Win7       C:\Users\<username>\AppData\Roaming\bazaar\2.0\rules


# the actual rules:

[name *.png]
eol = exact

[name *.pdf]
eol = exact

[name *.sh]
eol = lf

[name *]
eol = native