From: "Marc-F. Lucca-Daniau" <mfld.fr@gmail.com>
To: Marcin Laszewski <marcin.laszewski@gmail.com>
Cc: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: ELKS Split 2
Date: Fri, 21 Feb 2020 10:37:56 +0100 [thread overview]
Message-ID: <a14180d4-6e77-6421-eb11-d139d01e617a@gmail.com> (raw)
In-Reply-To: <CABdhv6KL4m7Pyyfr_J+aof_zrv76ZfrKAOCg5P4xHED9=v7WuQ@mail.gmail.com>
You are welcome, I like very much your optimization job to reduce the
sizes of the user land executables.
For the next patches, as I am not anymore one maintainer of the project,
I suggest to continue to post on this mailing list, or better to push a
PR in the upstream repository: https://github.com/jbruchon/elks
Starting from now, I will only participate to design discussions if they
are related to my field of interests, i.e. porting ELKS to embedded
systems and using it to train on optimization techniques.
Absolutely not interested in bloating ELKS to make it a general purpose
OS that does not fit in my flashed 8086 device.
About your funny citation : it looks like I was not a strong enough
dictator :-D :-D :-D !
MFLD
Le 21/02/2020 à 09:58, Marcin Laszewski a écrit :
> Thanks Marc,
>
> 2020-02-21 8:27 GMT+01:00, Marc-François Lucca-Daniau <mfld.fr@gmail.com>:
>> (...)
>> I am waiting for the situation to stabilize, then I will push your latest
>> commits to finish the job.
>> (...)
> That's why I prefer to stay away from project-managed.
> I have a few patches more. Have I wait & send you(?) it after full
> stabilization?
>
> ml.
>
> PS: In my opinion every community project has to have a strong
> dictator as a boss.
next prev parent reply other threads:[~2020-02-21 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABdhv6JxgbQ+3cq_gkt_hnSHZM+2MUtQZhJ1pVHK89uXXK6fEA@mail.gmail.com>
[not found] ` <CABdhv6KY1x+Cvg_5BUa=ONN1tJX0k9-sVRVmTi3JbvmM-LBSvQ@mail.gmail.com>
[not found] ` <CABdhv6K6F=vJ+sgpJozZn9A8Cm4CCoStinwVjg6X6iaxjC+=Lw@mail.gmail.com>
2020-02-20 18:15 ` ELKS Split 2 Marc-F. Lucca-Daniau
[not found] ` <CABdhv6LQD8gycegNQ2Ro+UP3PD9t6-pqHdqtLXjb=HwJr-1=Lw@mail.gmail.com>
[not found] ` <CACpuWUnu-He+kMQk3u0O=E3_EwPPXn6qaeTzRfQ9p9qk=Y1f+g@mail.gmail.com>
[not found] ` <CABdhv6KL4m7Pyyfr_J+aof_zrv76ZfrKAOCg5P4xHED9=v7WuQ@mail.gmail.com>
2020-02-21 9:37 ` Marc-F. Lucca-Daniau [this message]
2020-02-21 8:55 ` Marc-F. Lucca-Daniau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a14180d4-6e77-6421-eb11-d139d01e617a@gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=marcin.laszewski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).