Hi
there,
I'm a senior
embedded software engineer working for Eaton in New Zealand. We are
currently switching the IP stack in our products from a commercial stack to
LWIP. So far I'm quite pleased with the progress we've made and with LWIP
itself.
We are using the
head of the CVS repository and pulling that on a semi-regular basis into a
vendor branch in our own SVN repo.
I have a few
questions:
1. I saw that you
also have a GIT repository. Should we be using the head of that or are they
frequently synced? Which one is the master?
2. While integrating
LWIP into our software, we made a number of changes to fix bugs and improve
efficiency and I would like to contribute those back in order to minimize the
differences when I merge in changes from upstream. How should I go about doing
that? Are patches sent to this mailing list the best way?
3. One of the new
features we need to support is IPv6. I have succeeded enabling and compiling
IPv6 and have established an IPv6 based web connection with our product.
However, when I ran the IPv6ready logo test suite, it failed quite a large
number of tests. I am planning on going through these and fix as many as I think
are essential for good IPv6 operation. We do not (at this time) aim for an
actual certification, but I would like to have all failing tests understood and
documented. So my question is, who are the people that are currently working on
IPv6 (if any) and what is the best way for us to synchronize these efforts so we
do not duplicate the work and stomp on each others feed. Also, again, what is
the best way to submit changes I make? If it is necessary for me to send patches
to the mailing list, I may have to send them in larger batches. Direct
repository access might be more efficient and allow me to post changes daily.
However, I don't know how that fits with your policies etc.
4. Do you have a
coding std document, that I can review to avoid either having my patches
rejected because the code isn't formatted right or for someone to have to go
through them afterwards.
Cheers,
Seb