kicad-developers team mailing list archive

[Fabrizio Tappero <fabrizio.tappero@xxxxxxxxx>]

An other issue is that the current github setup require the
hypothetical contributor to have a github account.



On Fri, Mar 21, 2014 at 6:36 PM, Carl Poirier <carl.poirier.2@xxxxxxxxx> wrote:
> Maybe KiCad could be made to pull the new changes automatically ("git pull
> https://github.com/KiCad/kicad-library"; or "git fetch upstream" if it's a
> fork) on startup? However this would require the libraries to be installed
> in a user-writeable directory.
>
>
>
>
> On Fri, Mar 21, 2014 at 9:59 AM, Kaspar Emanuel <kaspar.emanuel@xxxxxxxxx>
> wrote:
>>
>> On 21 March 2014 08:10, Fabrizio Tappero <fabrizio.tappero@xxxxxxxxx>
>> wrote:
>> > When you get a repo because you want to contribute (either is kicad it
>> > self or the kicad lib repo) u clone the master repo, you do your
>> > modifications, you create and send to developers your patch, Done.
>> >
>> > Few days after your patch gets applied and ideally your would like to
>> > re-synch your current repo with the newest repo but it is not possible
>> > because your current repo is out of synch since you did your
>> > modifications locally.
>>
>> No, at this point you could switch your fp_lib_table to use the KiCad
>> github repo for that libary or keep it pointing to your local repo as
>> they should be the same. If there are additional changes in the KiCad
>> repo then you can pull those changes. If you have additional changes
>> since you made the patch you can make a new patch.
>>
>> >Maybe, some sort of intermediate tool that sits between the pcb guy
>> and git is needed?
>>
>> I think this is a good idea. Libgit2 could help with this.
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>