In response to a message written on 19.09.2015, 12:25, from Nick Østergaard:
Why do you need to include the revno? Who is using theese packages?
Because it's more human readable and memorable. In my preferred Linux
distribution packages are made from fixed archive. This is a compromise between
u
Den 19/09/2015 11.55 skrev "LordBlick" :
>
> In response to a message written on 19.09.2015, 00:16, from Mark Roszko:
>
>> Consecutive numbers which don't mean anything once you work on
>> multiple branches because they get reused. With git I can cherry-pick
>> commits globally across branches
In response to a message written on 19.09.2015, 00:16, from Mark Roszko:
Consecutive numbers which don't mean anything once you work on
multiple branches because they get reused. With git I can cherry-pick
commits globally across branches
OK, but I need include commit number in git archive f
In response to a message written on 19.09.2015, 10:31, from Nick Østergaard:
On my end it says: Invitations are sent via email and can be accepted
athttps://github.com/KiCad
OK, I'm in… ;)
--
Best Regards,
LordBlick
___
Mailing list: https://launchp
Den 19/09/2015 10.28 skrev "Nick Østergaard" :
>
>
> Den 19/09/2015 10.27 skrev "LordBlick" :
> >
> > In response to a message written on 19.09.2015, 09:55, from Nick
Østergaard:
> >
> >> >> But it seems that you have not accepted the invitaiton to the
team, and can
> >> >> therefore not push to
Den 19/09/2015 10.27 skrev "LordBlick" :
>
> In response to a message written on 19.09.2015, 09:55, from Nick
Østergaard:
>
>> >> But it seems that you have not accepted the invitaiton to the team,
and can
>> >> therefore not push to it. If you accept the invitation you should be
able to
>> >> p
In response to a message written on 19.09.2015, 09:55, from Nick Østergaard:
>> But it seems that you have not accepted the invitaiton to the team, and can
>> therefore not push to it. If you accept the invitation you should be able to
>> push.
>
> I've no idea, where I can accept it. My mai
Den 19/09/2015 09.50 skrev "LordBlick" :
>
> In response to a message written on 19.09.2015, 09:36, from Nick
Østergaard:
[1] https://github.com/KiCad/kicad-i18n
[2] https://code.launchpad.net/~kicad-developers/kicad/doc
>>
>> […]
>>
>> I guess you mean [1].
>
> You are right, my mis
In response to a message written on 19.09.2015, 09:36, from Nick Østergaard:
[1] https://github.com/KiCad/kicad-i18n
[2] https://code.launchpad.net/~kicad-developers/kicad/doc
[…]
I guess you mean [1].
You are right, my mistake.
But it seems that you have not accepted the invitaiton to the tea
2015-09-18 21:27 GMT+02:00 LordBlick :
> In response to a message written on 18.09.2015, 20:49, from Nick Østergaard:
>
>> Hi
>>
>> For your information the KiCad GUI translations has been moved to git
>> and hosted on github [1] under the KiCad organisation. Before they
>> were embedded in the old
In response to a message written on 18.09.2015, 20:49, from Nick Østergaard:
For your information the KiCad GUI translations has been moved to git
and hosted on github [1] under the KiCad organisation. Before they
were embedded in the old doc repository [2].
Mayby split that repo to every kicad-
Consecutive numbers which don't mean anything once you work on
multiple branches because they get reused. With git I can cherry-pick
commits globally across branches
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-devel
In response to a message written on 18.09.2015, 20:49, from Nick Østergaard:
Hi
For your information the KiCad GUI translations has been moved to git
and hosted on github [1] under the KiCad organisation. Before they
were embedded in the old doc repository [2].
Have a look at this thread [3] fo
Hi
For your information the KiCad GUI translations has been moved to git
and hosted on github [1] under the KiCad organisation. Before they
were embedded in the old doc repository [2].
Have a look at this thread [3] for background informaiton.
This means that no new commits shall be made on [2].
On Fri, May 22, 2015 at 03:47:54PM +0300, Fat-Zer wrote:
> I'm not really sure about that, so consider that as just a suggestion
> (not an advice):
> May be it would be nice to setup some online translation framework
> like pootle (http://pootle.translatehouse.org/) for either doc and
> gui.
> I ha
Dashie,
I believe the reason why the Mac build doesn't use /usr/local/* by default
is that on Mac, we want the docs inside the bundle, not located somewhere
else in the system. I do this through a script for the nightlies, but if
you know/can think of a good way to do this through CMake in the doc
> Le 22 mai 2015 à 13:20, jp charras a écrit :
>
> Le 22/05/2015 09:25, Dashie a écrit :
>> Hi all,
>>
>> I’ve seen the kicad-doc project which i will be helping with French
>> translations, but i’ve seen that the GUI isn’t fully translated or
>> have « fatal » errors [1].
>>
>> I’ve been unab
2015-05-22 14:20 GMT+03:00 jp charras :
> Le 22/05/2015 09:25, Dashie a écrit :
> Thanks for your interest in Kicad.
>
> GUI French translation is up to date.
> If you have issues with it, you are not using the lasted versions of
> Kicad or dictionaries (or files mismatch).
>
> When making GUI tran
Le 22/05/2015 09:25, Dashie a écrit :
> Hi all,
>
> I’ve seen the kicad-doc project which i will be helping with French
> translations, but i’ve seen that the GUI isn’t fully translated or
> have « fatal » errors [1].
>
> I’ve been unable to see where in the code translations where, anyone
> can
Hi all,
I’ve seen the kicad-doc project which i will be helping with French
translations, but i’ve seen that the GUI isn’t fully translated or have « fatal
» errors [1].
I’ve been unable to see where in the code translations where, anyone can point
me how to find them to help ?
[1]: When in
20 matches
Mail list logo
