kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

On 11/13/2013 02:23 PM, Carl Poirier wrote:
> I indeed did not have that rules file. Are you sure everything is alright on that front?

No, not 100%, only 85% sure.

It pertains to line endings.

Maybe you lucked out because you are working on linux and no '\r' were introduced.  Had
you been on Windows, then last guy wins.  (Unless the rules file is in play, then the repo
is '\n' but platform dependent in the working copy.)

What I used to detect the problem before was bzr st or bzr diff, immediately after a
branch or checkout.  It would show essentially every line of every file.

85% is a high degree of certainty however.



> I'll make sure it's installed for next time.
> 
> I'll take care of the rest in one other batch. I understand how disruptive it can be, but
> I wanted to make sure everything was alright. I'll skip the .wrl files for the rest.

Or defer that work.  So we can get past the more disruptive aspect sooner.  Then go back
and make a sweep not pertaining to fp-lib-table.

Thanks

> 
> As for the description, for now I'm putting in there whatever part number was in the
> library name, and ditching the blue_shirt_and_eating_pizza stuff. I can surely however
> write some more complete descriptions for each of them!
> 
> 
> On Wed, Nov 13, 2013 at 2:29 PM, Dick Hollenbeck <dick@xxxxxxxxxxx
> <mailto:dick@xxxxxxxxxxx>> wrote:
> 
> 
>     >
>     > It might be a bit off-topic but this looks like a place where github
>     > and pull requests would be helpful to make it easy to review and merge
>     > work by the integrator and let the committer do the work to ensure
>     > things are in the right format for pulling.
>     >
>     > Chris
> 
>     Yes, I am all in favor of moving all the libraries to github.  Someone needs to setup a
>     project there.
> 
>     As the *.mod files are moved, Carl has a script to convert them all to *.pretty format, so
>     those footprint libraries can then be accessed either by installing them or by using the
>     GITHUB_PLUGIN.
> 
>     There is still no GITHUB_PLUGIN support for OSX.
> 
>     Summary:
> 
>     a) someone needs to create the github project.
> 
>     b) someone needs to build GITHUB_PLUGIN on OSX.
> 
>     Just talking and making suggestions is a far cry from that.
> 
>     Carl at least stepped up.
> 
> 
> 
> 
> 
> 
>