> -Original Message-
> From: Gregory Nutt
> Sent: Tuesday, May 26, 2020 2:13 AM
> To: dev@nuttx.apache.org
> Subject: Re: kconfig (Re: mbedtls)
>
>
> > I agree, and all the more reason we should ensure that our project has
> > a controlled snapshot
ifferent opinions.
> Original message From: Takashi Yamamoto
> Date: 5/25/20 6:41 PM (GMT-06:00) To:
> dev@nuttx.apache.org Subject: Re: kconfig (Re: mbedtls) On Tue, May 26, 2020
> at 12:48 AM Gregory Nutt wrote:>> We should all be
> using a consistent, common vers
On Tue, May 26, 2020 at 10:11 AM Nathan Hartman
wrote:
>
> On Mon, May 25, 2020 at 8:41 PM Takashi Yamamoto
> wrote:
>
> > On Tue, May 26, 2020 at 12:48 AM Gregory Nutt wrote:
> > >
> > > We should all be using a consistent, common version of
> > > kconfig-frontends. A snapshot was taken and ha
t: Re: kconfig (Re: mbedtls) On Tue, May 26, 2020 at
12:48 AM Gregory Nutt wrote:>> We should all be using a
consistent, common version of> kconfig-frontends. A snapshot was taken and has
never disappeared from> internet contrary to other statements it is always been
here and wil
On Mon, May 25, 2020 at 8:41 PM Takashi Yamamoto
wrote:
> On Tue, May 26, 2020 at 12:48 AM Gregory Nutt wrote:
> >
> > We should all be using a consistent, common version of
> > kconfig-frontends. A snapshot was taken and has never disappeared from
> > internet contrary to other statements it i
On Tue, May 26, 2020 at 12:48 AM Gregory Nutt wrote:
>
> We should all be using a consistent, common version of
> kconfig-frontends. A snapshot was taken and has never disappeared from
> internet contrary to other statements it is always been here and will
> always be here: https://bitbucket.org/
I agree, and all the more reason we should ensure that our project has
a controlled snapshot of this tool -- and to ensure the longevity of
that snapshot so that it will not be lost suddenly!
There is also a snapshot of genromfs in the tools repository. This is a
snapshot of the tool from th
On Mon, May 25, 2020 at 12:28 PM Gregory Nutt wrote:
> Most projects that use kconfig-frontends use a snapshot version that is
> built into the codebase. We cannot do that because kconfig-frontends is
> GPL. However, I still argue that we should use a fixed, common version
> of kconfig-frontends
On Mon, May 25, 2020 at 11:48 AM Gregory Nutt wrote:
A snapshot was taken and has never disappeared from
internet contrary to other statements it is always been here and will
always be here: https://bitbucket.org/nuttx/tools/src/master/
Correct. I meant that the original (from Yann Morin) di
On 5/25/2020 10:03 AM, Nathan Hartman wrote:
On Mon, May 25, 2020 at 11:48 AM Gregory Nutt wrote:
A snapshot was taken and has never disappeared from
internet contrary to other statements it is always been here and will
always be here: https://bitbucket.org/nuttx/tools/src/master/
Correct. I m
On Mon, May 25, 2020 at 11:48 AM Gregory Nutt wrote:
> A snapshot was taken and has never disappeared from
> internet contrary to other statements it is always been here and will
> always be here: https://bitbucket.org/nuttx/tools/src/master/
Correct. I meant that the original (from Yann Morin) d
We should all be using a consistent, common version of
kconfig-frontends. A snapshot was taken and has never disappeared
from internet contrary to other statements it is always been here and
will always be here: https://bitbucket.org/nuttx/tools/src/master/
Since the kconfig-frontends pro
We should all be using a consistent, common version of
kconfig-frontends. A snapshot was taken and has never disappeared from
internet contrary to other statements it is always been here and will
always be here: https://bitbucket.org/nuttx/tools/src/master/
We do not accept any Python-based
On Mon, May 25, 2020 at 12:36 AM Takashi Yamamoto
wrote:
> On Mon, May 25, 2020 at 1:00 AM Nathan Hartman
> wrote:
> > We do have to solve the issue of Kconfig. That has disappeared from
> > the Internet and we depend on it. We were told, before we joined
>
> do we have some reasons not to switc
On Mon, May 25, 2020 at 1:00 AM Nathan Hartman wrote:
>
> On Sun, May 24, 2020 at 7:58 AM Alan Carvalho de Assis
> wrote:
> > Some months ago I suggested that NuttX could focus only in the kernel
> > and we could create an external distribution using some build system
> > like buildroot, yocto, e
15 matches
Mail list logo
