Hi Simon,

I also didn't quite get what Roberto was trying to say, but I *think* he tried to inform you that the upstream BusyBox picks up patches _reeally_ slowly. There are regularly 1-2 year old patches getting submitted over and over again on this list. From what I understand, the whole project is maintained by like 2 people.

What he linked is his, and Nadav Tasher's fork of BusyBox. Nadav has been very active here on the list, trying to get his changes upstreamed as well. And I'm guessing Roberto is collecting contributions like this in his own fork. But frankly I think if he wants to collect yours, he'll be able to get it from here in the list.

Anyways, you were right to post here, however, I'd like to add that you should either use `git send-email` to send a plaintext mail containing the patch, or attach it as a file. Formatted mail does not play well with `git am`.

Bence

On 2025. 06. 25. 9:17, Simon Ungar Felding wrote:
Hi Roberto, thanks for your message! I'm not sure I understand. Should I not post a patch on here to implement it, and instead start on github?

Sent from Outlook for Android <https://aka.ms/AAb9ysg>

------------------------------------------------------------------------
*From:* Roberto A. Foglietta <roberto.foglie...@gmail.com>
*Sent:* Monday, April 28, 2025 9:46:26 am
*To:* Simon Ungar Felding <s...@adm.ku.dk>
*Cc:* busybox@busybox.net <busybox@busybox.net>
*Subject:* Re: New applet suggestion: envsubst

        
Du får ikke ofte mails fra roberto.foglie...@gmail.com. Få mere at vide om, hvorfor dette er vigtigt <https://aka.ms/ LearnAboutSenderIdentification>
        



On Sun, 27 Apr 2025 at 13:21, Simon Ungar Felding <s...@adm.ku.dk <mailto:s...@adm.ku.dk>> wrote:

    Hi Busybox maintainers!


These kinds of patches are very interesting in terms of "self-contained" stuff.

Feel free to propose them also for being integrated into

https://github.com/robang74/BusyBox-by-NT <https://github.com/robang74/ BusyBox-by-NT>

https://github.com/NadavTasher/BusyBox <https://github.com/NadavTasher/ BusyBox>

In case that "fork" word appears, take in consideration that FOSS is about forks and integrations, since the beginning. Moreover, forks and integrations are THE essence of FOSS, and who see a "fork" like a threat is doing politics. So, skip the "fork" debate entirely and spread the code. Usually, in mainstream or somewhere else it pops up something better.

Best regards, R-





_______________________________________________
busybox mailing list
busybox@busybox.net
https://lists.busybox.net/mailman/listinfo/busybox


_______________________________________________
busybox mailing list
busybox@busybox.net
https://lists.busybox.net/mailman/listinfo/busybox

Reply via email to