Hi Adam
If the current 5.1 nightly build jobs are to be used again, maybe we
can enable it now to see what we are missing? Assuming there is enough
build capacity available.
Nick
On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote:
>
> Hi folks!
>
> My KiCad time has been dramatically reduced for the
[1]: https://gitlab.com/kicad/code/kicad/-/issues/4169
On 4/7/20 10:57 AM, Wayne Stambaugh wrote:
> Adam,
>
> No problem. A new macOS crash bug[1] just reared it's ugly head so we
> will have get this fixed before we freeze for 5.1.6 so you have some
> time to get the OCC switchover completed.
Adam,
No problem. A new macOS crash bug[1] just reared it's ugly head so we
will have get this fixed before we freeze for 5.1.6 so you have some
time to get the OCC switchover completed. Thanks for working on this
and stay safe.
Cheers,
Wayne
On 4/7/20 10:16 AM, Adam Wolf wrote:
> Hi folks!
>
Thank you very much for the effort!
On Tue, 7 Apr 2020 at 16:16, Adam Wolf wrote:
>
> Hi folks!
>
> My KiCad time has been dramatically reduced for the past month due to
> schools closing for COVID-19.
>
> I hope to have the OCC switchover complete this week--there were some
> fixup_bundle snags
Hi folks!
My KiCad time has been dramatically reduced for the past month due to
schools closing for COVID-19.
I hope to have the OCC switchover complete this week--there were some
fixup_bundle snags again. (I swear this whole fiasco ends with me
joining the CMake macOS team...) After the OCC sw
I just want to give everyone a quick heads up. Between tomorrow and
until after KiCon is over I will be really busy at work and getting
ready for KiCon so I will most likely not be as available as I normally
am. If you don't hear from me promptly please be patient. I will do my
best to prioritiz
2015-01-06 14:48 GMT+01:00 Wayne Stambaugh :
> On 1/5/2015 7:28 PM, Adam Wolf wrote:
>> I think that is a good idea.
>>
>> Is our "coding standard checker" script still working well?
>
> I haven't used uncrustify in a while so I'm not sure. The last time I
> did use it, it seemed to handle everyth
On 1/5/2015 7:28 PM, Adam Wolf wrote:
> I think that is a good idea.
>
> Is our "coding standard checker" script still working well?
I haven't used uncrustify in a while so I'm not sure. The last time I
did use it, it seemed to handle everything OK except the _() macros
which for some reason the
I think the uncrustify script is working well.
I tested it on the pcbnew/eagle_plugin.cpp which I am going to make a
patch for, but it did change a lot, like making multiline comments to
have asterisks in each line. So will it be better to submit a patch
for the functional changes, such that they
I think that is a good idea.
Is our "coding standard checker" script still working well?
Adam Wolf
On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard wrote:
> Hi Wayne
>
> I was just looking at the coding style policy in
> Documentation/coding_style_policy.pdf and think the format (pdf) is
> not
Hi Wayne
I was just looking at the coding style policy in
Documentation/coding_style_policy.pdf and think the format (pdf) is
not that great for linking and sharing to newcomers.
Would it be a good idea to convert it to md for the use in the
doxygen-docs along side the roadmap and stable realease
11 matches
Mail list logo
