Hi community,
I believe we have reached a consensus in this mail thread. Please allow me
to end the current vote. The final result is:
+1: 9
+0: 3
-1: 0
Thanks everyone for your valuable comments.
cc @lupyuen
BRs,
chao an 于2025年4月7日周一 17:13写道：
> Hi community,
>
> Some green hand and individua
+1
On Mon, 7 Apr 2025, 17:28 Maciej Wójcik, wrote:
> +1
>
> Am Mo., 7. Apr. 2025 um 16:49 Uhr schrieb Laczen JMS >:
>
>> +1
>>
>> On Mon, Apr 7, 2025, 11:36 chao an wrote:
>>
>>> Hi community,
>>>
>>> Some green hand and individual developer who are not familiar with nuttx
>>> may be confused
@sebastien
Thanks for your opinion. I think I need to add more information to make
everyone clear about the purpose of this change.
BRs,
Sebastien Lorquet 于2025年4月7日周一 21:39写道：
> There was a lot of comments in the github and I may have missed the whole
> of it.
>
> Your information was reassuri
+1
On Mon, Apr 7, 2025 at 6:13 AM chao an wrote:
> Hi community,
>
> Some green hand and individual developer who are not familiar with nuttx
> may be confused by the naming of modlib, in currect implement, modlib as an
> elf loader and parser, does not provide any features other than elf.
>
> I
+1
pon., 7 kwi 2025 o 16:12 Alan C. Assis napisał(a):
> +1
>
> On Mon, Apr 7, 2025 at 6:13 AM chao an wrote:
>
>> Hi community,
>>
>> Some green hand and individual developer who are not familiar with nuttx
>> may be confused by the naming of modlib, in currect implement, modlib as an
>> elf lo
Hello world :-)
Sorry for a bit of absence I was out for a delegation getting back to
the living :-)
0 from me not to block as there is a preference towards change and it
seems remaining part of the bigger update in progress that should be
closed.. if the community prefers to have it in the minor
On Wed, Apr 9, 2025 at 9:22 AM Tomek CEDRO wrote:
>
> Hi Takashi :-)
>
> There were long discussions on the mailing list, then voting, then
> discussion on the PR, and comes after lots of breaking changes being
> too freely merged into the upstream, sometimes with laconic
> description and sometim
This change has no functional impact, so it does not meet the "absolutely
necessary and unavoidable" constraint.
But this commit will affect everyone's understanding of the kernel's key
features, which is a good thing in further. I think it meets the "necessary
and unavoidable" constraint.
In addit
On Thu, Apr 10, 2025 at 10:44 AM chao an wrote:
> Yamamoto san, there may be some objective factors here, but we may already
> be on the way to voting. could you please vote again based on the changes
> from the "code" perspective?
>
i've read CONTRIBUTING.md 1.12 and 1.13 a few times.
but i don
@yamamoto Thanks for your comments!
BRs,
Takashi Yamamoto 于2025年4月10日周四 11:37写道：
>
>
> On Thu, Apr 10, 2025 at 11:55 AM chao an wrote:
>
>> This change has no functional impact, so it does not meet the "absolutely
>> necessary and unavoidable" constraint.
>> But this commit will affect everyon
On Thu, Apr 10, 2025 at 11:55 AM chao an wrote:
> This change has no functional impact, so it does not meet the "absolutely
> necessary and unavoidable" constraint.
> But this commit will affect everyone's understanding of the kernel's key
> features, which is a good thing in further. I think it
Yamamoto san, there may be some objective factors here, but we may already
be on the way to voting. could you please vote again based on the changes
from the "code" perspective?
BRs,
Takashi Yamamoto 于2025年4月9日周三 06:56写道：
> -1
>
> reading the recently added text in CONTRIBUTING.md,
> this chang
Hi Takashi :-)
There were long discussions on the mailing list, then voting, then
discussion on the PR, and comes after lots of breaking changes being
too freely merged into the upstream, sometimes with laconic
description and sometimes without even testing. This is to focus more
on long term self
On Wed, Apr 9, 2025 at 9:22 AM Tomek CEDRO wrote:
>
> Hi Takashi :-)
>
> There were long discussions on the mailing list, then voting, then
> discussion on the PR, and comes after lots of breaking changes being
> too freely merged into the upstream, sometimes with laconic
> description and sometim
-1
reading the recently added text in CONTRIBUTING.md,
this change doesn't seem even eligible for voting because
it is not "absolutely necessary and unavoidable".
i personally like the change itself and prefer loosening the rules in
CONTRIBUTING.md though.
On Mon, Apr 7, 2025 at 6:13 PM chao an
> > > If you prefer modlib, please reply with -1.
> > > If you recommend libelf, please reply with +1.
Rules for voting are a little different for code changes.
The required Apache voting process is here:
https://www.apache.org/foundation/voting.html
For code changes, that document says: "Vot
+1
On Tue, Apr 8, 2025 at 8:55 AM Tiago Medicci Serrano
wrote:
>
> +1
>
> Em seg., 7 de abr. de 2025 às 21:16, Yanfeng Liu
> escreveu:
>
> > +1
> > On Mon, 2025-04-07 at 17:13 +0800, chao an wrote:
> > > Hi community,
> > >
> > > Some green hand and individual developer who are not familiar with
+1
Em seg., 7 de abr. de 2025 às 21:16, Yanfeng Liu
escreveu:
> +1
> On Mon, 2025-04-07 at 17:13 +0800, chao an wrote:
> > Hi community,
> >
> > Some green hand and individual developer who are not familiar with nuttx
> > may be confused by the naming of modlib, in currect implement, modlib as
>
+1
On Mon, 2025-04-07 at 17:13 +0800, chao an wrote:
> Hi community,
>
> Some green hand and individual developer who are not familiar with nuttx
> may be confused by the naming of modlib, in currect implement, modlib as an
> elf loader and parser, does not provide any features other than elf.
>
+1
Am Mo., 7. Apr. 2025 um 16:49 Uhr schrieb Laczen JMS :
> +1
>
> On Mon, Apr 7, 2025, 11:36 chao an wrote:
>
>> Hi community,
>>
>> Some green hand and individual developer who are not familiar with nuttx
>> may be confused by the naming of modlib, in currect implement, modlib as an
>> elf loa
+1
On Mon, Apr 7, 2025, 11:36 chao an wrote:
> Hi community,
>
> Some green hand and individual developer who are not familiar with nuttx
> may be confused by the naming of modlib, in currect implement, modlib as an
> elf loader and parser, does not provide any features other than elf.
>
> In th
Hello,
This rename:
- breaks several build you had to fix incrementally
- it fixes nothing not the name.
The modlib name is unfortunate but I think we can live with it.
Also why is the commit showing the name as "ELF" and not "LIBELF"?
That is not acceptable for me. Also -1.
However, I
There was a lot of comments in the github and I may have missed the
whole of it.
Your information was reassuring, I am not opposing it anymore.
Care is being taken about this issue, that is the most important of all.
Sebastien
On 07/04/2025 15:35, chao an wrote:
@ Sebastien Lorquet
> - br
@ Sebastien Lorquet
> - breaks several build you had to fix incrementally
> However, I see a genuine concern from many members around this change,
actual tests are being made and additional required fixes have been found.
> Also communication efforts have been made beforehand.
This commit does n
+1
Lup
On Mon, Apr 7, 2025 at 5:13 PM chao an wrote:
> Hi community,
>
> Some green hand and individual developer who are not familiar with nuttx
> may be confused by the naming of modlib, in currect implement, modlib as an
> elf loader and parser, does not provide any features other than elf.
Hi community,
Some green hand and individual developer who are not familiar with nuttx
may be confused by the naming of modlib, in currect implement, modlib as an
elf loader and parser, does not provide any features other than elf.
In this pull request, I plan to rename modlib to elf, and adjust
26 matches
Mail list logo
