ble. I guess some _(...) magic is missing here? I have no full
knowledge about what needs to be changed here, thus I can't contribute a
patch.
--
Regards
Carsten Schoenert
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-deve
essage. You need some grepping at all and given the magic
the content is written at the end of the commit message you can simply
search for NEW|CHANGE|REMOVE and take the whole text beginning with that
line.
--
Regards
Carsten Schoenert
___
Maili
ed that.
As far I know it was also possible to ask Jeremy to get an instance on
patchwork.ozlabs.org [2].
[1] http://jk.ozlabs.org/projects/patchwork/
https://github.com/getpatchwork/patchwork
[2] http://patchwork.ozlabs.org/
--
Regards
Carsten Schoenert
_
on why you have done all that work will go
down under in the typical noise of the mailing list and nobody but you
will later know why the single commit was made.
--
Regards
Carsten Schoenert
___
Mailing list: https://launchpad.net/~kicad-developers
Post t
act in every PO
file down in the various languages. So I don't really want to put again
some energy on that before things are clear.
We need some agreement first what needs or should be added to the
documentation of KiCad5. If there is something like that existing we
than need people who take care
documentation part.
A Etherpad site could be a starting scratch notepad, someone can pick up
the notes then into a KiCad wiki site on GitHub?
--
Regards
Carsten Schoenert
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@l
rrect knowledge about the new features) I can't help much here. But I
wanted to raise my concerns about this missing thing.
Is here something planned or someone has started to work in this corner
and/or is there a place this is tracked? There are only about three
months left until FOSDEM.
--
place is to
discuss your questions in detail on that extra list. I encourage you to
join the team if you want to contribute regularly.
https://launchpad.net/~kicad-doc-devs
PS: I've started to prepare a update of the German KiCad translation for
the nightly some days ago, but I've not finished
branch and tagged releases
would be fine and enough. The l10n and documentation part is already
using this model.
--
Regards
Carsten Schoenert
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.
using git-svn package.
And this is even more slower than plain svn. ;-(
--
Regards
Carsten Schoenert
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developer
an decide what the
content is and where it needs to be locally stored.
That brings then the question, we need to be clear how and where to
store such local data. And that of course for all operating systems.
(PS: Please cut of that unneeded data if top posting is
y suggests that the gEDA license is the way to go.
this wording is potential ambiguous!
There is no gEDA license, we just can talk about a analogous gEDA
licensing model.
http://wiki.geda-project.org/geda:license
--
Regards
Carsten Schoenert
___
site. All those user are depending on
off line downloads and on new released versions.
>From a users POV it's than hard to understand that libraries and there
structure of them have changed a lot between two micro versions!
[1] https://www.debian.org/social_co
201 - 213 of 213 matches
Mail list logo
