On 05/30/2013 03:12 PM, Dick Hollenbeck wrote: > On 05/30/2013 01:16 PM, Dick Hollenbeck wrote: >> On 05/30/2013 08:30 AM, Kerusey Karyu wrote: >>> Hi. >>> >>> I applied "rules" to Bazaar as You suggest below: >>> >>>> Gang, >>>> >>>> Please put the attached file into your BZR_HOME directory and name it >>> rules. >>>> >>> >>> OK. I assume that these rules are strict for Kicad Developpers team who >>> maintain the code and should respect the coding policy. But what about >>> of library developers/commiters or doc writers/translators? Does it make >>> some influence to us? >> >> "rules" affects bzr as a program. If they are in play, then any repo >> accessed will be >> subject to the rules in play. Any bzr repo, kicad or not, testing, or lib. >> >> >> Our "rules" work best when: >> >> (A) the repo has LF for text file line endings, and >> (B) working tree has "native" line endings. >> >> Native means: >> LF on linux/unix >> CRLF on Windows >> >> To get a repo to have LF line endings, requirement (A) above, take these >> steps: >> >> 0) put "rules" into affect >> 1) start in dir <lib-repo> >> 2) bzr up >> 3) cd .. >> 4) branch <lib-repo> lf-repo > > oops: > 4) bzr branch <lib-repo> lf-repo > >> 5) cd lf-repo >> 6) bzr ci -m 'convert text files to LF endings in repo' >> 7) bzr push lp:~kicad-lib-committers/kicad/library >> >> Never use push again. > > 8) cd ../<lib-repo> > 9) bzr up > 10) cd .. > 11) rm -rf lf-repo
Since no one took the initiative, I did this now for lp:~kicad-lib-committers/kicad/library _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp