Re: [lwip-devel] IPv6 support and source code access

[David Empson]

address@hidden wrote:
> 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?

LWIP recently switched from using CVS to GIT. The CVS repository is no
longer being updated and its current HEAD is out of date. You should switch
to using GIT.

> 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?

Patches and bug fixes are submitted using the bug tracker on Savannah.

https://savannah.nongnu.org/projects/lwip/

You need to be logged in using your Savannah account (create one first if
necessary), then click on the Bugs or Patches menus to browse the current
items or submit new ones.

Note that because you are probably working from outdated code from CVS, you
should update your code from the latest changes in GIT before submitting any
bug fixes or patches, otherwise you might be duplicating a bug which has
already been fixed.

(I can't answer your questions on IPv6 or coding standards, as I'm not one 
of the LWIP developers, just another user.)