[lwip-users] Re: [lwip] File structure regarding sioslipif and eventually pppi f

[Scott Robinson]

--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Personally, I think it's a logical idea. Since lwIP is targetted at embedded
systems, I can imagine more than a few environments supportin only 8.3. (or
less)

Scott.

* Adam Dunkels translated into ASCII [Mon, Oct 21, 2002 at 08:28:46PM +0200=
][<address@hidden>]
> Hi!
>=20
> On Mon, 2002-10-21 at 20:08, Scott Robinson wrote:
> > I think he meant renaming the file names themselves.
>=20
> Ooops, of course... :-P
>=20
> What do you others think about renaming the files? I don't see any major
> problems with doing so, especially if it increases portability. The only
> other files with names longer than 8.3 is ethernetif.{c,h} and
> sioslipif.{c,h} which will be renamed anyway.
>=20
> /adam
> --=20
> Adam Dunkels <address@hidden>
> http://www.sics.se/~adam/
>=20
> [This message was sent through the lwip discussion list.]

--=20
http://quadhome.com/           - Personal webpage
tranzoa.net                    - Firewall

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s: a--- C++ UL+++ P++ L+++ E- W++ N++ o+ K++ w++=20
O M V(-) PS+ PE Y+ PGP+++ t@ 5 X- R- tv(-) b++++ DI++++ D+=20
G e* h! r* y=20
------END GEEK CODE BLOCK------

--r5Pyd7+fXNt84Ff3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iEYEARECAAYFAj20pO0ACgkQ+1+mlYgeODczIACfTrr+xHXLy7wzoxxbWrRRLMl2
xqoAoI8+qm+HtfBLWoiS37OiARAvAkv7
=jbDC
-----END PGP SIGNATURE-----

--r5Pyd7+fXNt84Ff3--
[This message was sent through the lwip discussion list.]