BTW, can someone please remove the !@#$ Reply-to header in the apache mailing lists? It completely breaks messages that are cross posted, effectively stealing all replies from all other mailing lists, as well as from anyone that was CC'd that doesn't happen to be on the Apache mailing list.
On Wed, Aug 30, 2017 at 10:08:50PM +0200, Andrzej Kaczmarek wrote:
I'm now porting NFFS code to Zephyr and in order to avoid forking this code into two separate projects I'd like to propose to move NFFS code into its own repository (i.e. mynewt-nffs) and basically make it a bit more generic so it can be used by other projects.
I think this is a good idea. We'll need to figure out what project to host it under.
In case of Mynewt, there's not much to do since everything is already implemented and just needs to be copied from one place to another. The API can be polished over time and memory usage (heap vs. static) can be made configurable.
Mynewt has the distinct advantage of its build system being able to pull code in from other repos. This is nice because it means this separation isn't difficult to do.
Of course the new repository would be compatible with Mynewt ootb, the changes in code are to make "copying" it to other OS-es as straightforward as possible so code can be updated to new release easily.
Is your intent then to just drop this code into the Zephyr repository (probably under 'ext') and manually keeping it up to date, like is done now. We should probably bring this up on the Zephyr mailing list as well. Unless the Reply-to problem is fixed with the Mynewt mailing lists, you should probably just send it to that list (right now, the Mynewt mailing list will steal any other address you To or Cc a message to, redirecting all replies only to that list). David
