kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

As to the outstanding patches, I think they’re all mine.

The code-review fixes for the update footprints one [1] are the most likely to have merge issues.

The OSX cursor-shape one [2] has already suffered a merge failure between two of my branches.  But I think it’s been reviewed and the merge-wreck-repairs are ready to go.

The OSX event-loop issue is the highest priority, but it’s a single-location four-liner [3], so it can easily be merged/redone/whatever if necessary.

I’m currently working on a 6.0 feature to do item highlighting when hovering over conflict items in DRC, so there should be a lull in my 5.0 patch posting (unless a regression or something critical comes in).

Cheers,
Jeff.

[1] https://bugs.launchpad.net/kicad/+bug/1466857
[2] https://bugs.launchpad.net/kicad/+bug/1745097
[3] https://bugs.launchpad.net/kicad/+bug/1718079


> Sure.
> 
> Currently I have a fix for cvpcb.
> This is a very low risk change, and a test case.
> An other low risk is the common files.
> 
> The main risk is for Pcbnew files.
> 
> So, if I am the guy who make the job, I am thinking to commit 3 or 4 more basic changes in Pcbnew tree.
> 
> About merge issues, I know a few recent patches are not yet merged and not yet reviewed.
> So, it could be worth to know what patches are still pending.
> 
> 
> -- 
> Jean-Pierre CHARRAS
> 
> _______________________________________________
> 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