From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos + lwip
Date: Sun, 02 Aug 2009 17:24:00 -0000 [thread overview]
Message-ID: <b18c5f790908021024t355818bfuabe4d9c6658bdcdc@mail.gmail.com> (raw)
In-Reply-To: <8fef83b30907311156w5868ca26j1554f2c8805e1f82@mail.gmail.com>
On Sat, Aug 1, 2009 at 12:26 AM, Sergei
Gavrikov<sergei.gavrikov@gmail.com> wrote:
> Mandeep Sandhu wrote:
>>
>> I see the following in the Changelog file
>> (packages/net/lwip_tcpip/v3_0/ChangeLog)
>>
>> 2006-03-26 Uwe Kindler <uwe_kindler@web.de>
>>
>> * Updated the complete lwIP source to the latest lwIP
>> CVS version 1.1.1
>>
>> So this means it's using rel 1.1.1...No?
>
> Hi Mandeep,
>
> eCos community has a few lists:
> http://ecos.sourceware.org/intouch.html
>
> The most of the patches (improvements) are discussed in
> in the ecos-patches list, so, it was easy to answer:
> http://ecos.sourceware.org/ml/ecos-patches/2006-03/
>
> So, yes, it does mean.
Ok. And thanks for pointing me to the intouch list.
Regards,
-mandeep
>
> Sergei
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-08-02 17:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 13:10 Mandeep Sandhu
2009-07-30 13:51 ` Sergei Gavrikov
2009-07-31 5:44 ` Mandeep Sandhu
2009-07-31 18:56 ` Sergei Gavrikov
2009-08-02 17:24 ` Mandeep Sandhu [this message]
2009-08-26 11:01 Mandeep Sandhu
2009-08-26 11:16 ` Simon Kallweit
2009-08-27 10:49 ` Mandeep Sandhu
2009-08-27 11:17 ` Simon Kallweit
2009-08-27 12:42 ` Mandeep Sandhu
2009-08-27 13:20 ` Mandeep Sandhu
2009-08-27 13:42 ` Simon Kallweit
2009-08-27 13:51 ` Mandeep Sandhu
2009-08-27 14:02 ` Mandeep Sandhu
2009-08-27 14:06 ` Simon Kallweit
2009-08-27 14:47 ` Sergei Gavrikov
2009-08-27 15:03 ` Sergei Gavrikov
2009-09-01 12:04 ` Mandeep Sandhu
2009-09-01 12:17 ` Simon Kallweit
2009-09-01 12:32 ` Mandeep Sandhu
2009-09-01 12:38 ` Simon Kallweit
2009-09-01 12:49 ` Mandeep Sandhu
2009-09-01 12:57 ` Simon Kallweit
2009-09-01 13:25 ` Mandeep Sandhu
2009-09-01 13:34 ` Simon Kallweit
2009-09-01 15:20 ` Mandeep Sandhu
2009-09-01 15:32 ` Simon Kallweit
2009-09-01 15:46 ` Mandeep Sandhu
2009-09-01 15:49 ` Simon Kallweit
2009-09-02 6:15 ` Mandeep Sandhu
2009-09-02 13:19 ` Mandeep Sandhu
2009-09-02 15:32 ` Simon Kallweit
2009-09-03 7:45 ` Mandeep Sandhu
2009-09-03 8:36 ` Simon Kallweit
2009-09-03 8:46 ` Mandeep Sandhu
2009-09-03 8:48 ` Simon Kallweit
2009-09-03 8:55 ` Mandeep Sandhu
2009-09-03 9:04 ` Simon Kallweit
2009-09-03 10:23 ` Mandeep Sandhu
2009-09-03 10:46 ` Sergei Gavrikov
2009-08-27 13:52 ` Sergei Gavrikov
2009-08-27 14:05 ` Simon Kallweit
2009-08-27 14:42 ` Bart Veer
2009-08-27 14:54 ` Sergei Gavrikov
2009-08-27 13:45 ` Sergei Gavrikov
2009-08-27 13:49 ` Mandeep Sandhu
2009-08-27 14:04 ` Simon Kallweit
[not found] <144735.17263.qm@web65404.mail.ac4.yahoo.com>
2009-08-27 14:11 ` Simon Kallweit
2009-08-27 14:20 agfa prayoga s
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b18c5f790908021024t355818bfuabe4d9c6658bdcdc@mail.gmail.com \
--to=mandeepsandhu.chd@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=sergei.gavrikov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).