On 2016-05-02 09:57 +0200, Christian Mauderer wrote:
>
> Just two thoughts on the tools. Both doesn't need instant answers.
> Please note that I don't intend to contradict the tools.
>
> I just took a quick glance on the linked pages but from that it seems
> that both tools are quite git-centered
Am 02.05.2016 um 01:42 schrieb Amar Takhar:
> On 2016-04-29 17:39 +1000, Chris Johns wrote:
>
>> I had a long chat to Amar about this topic today and he told me we
>> should follow the FreeBSD model for vendor software. FreeBSD has
>> https://svnweb.freebsd.org/base/vendor/ and it contains the
On Sun, May 1, 2016 at 7:42 PM, Amar Takhar wrote:
> On 2016-04-29 17:39 +1000, Chris Johns wrote:
>
>> I had a long chat to Amar about this topic today and he told me we
>> should follow the FreeBSD model for vendor software. FreeBSD has
>> https://svnweb.freebsd.org/base/vendor/ and it contains
On 2016-04-29 17:39 +1000, Chris Johns wrote:
> I had a long chat to Amar about this topic today and he told me we
> should follow the FreeBSD model for vendor software. FreeBSD has
> https://svnweb.freebsd.org/base/vendor/ and it contains the vendor
> source untouched and then the version used
Am 29.04.2016 um 09:39 schrieb Chris Johns:
> On 29/04/2016 16:19, Christian Mauderer wrote:
>> Am 29.04.2016 um 02:45 schrieb Chris Johns:
>>> On 28/04/2016 18:27, Christian Mauderer wrote:
Am 27.04.2016 um 02:07 schrieb Chris Johns:
> On 26/04/2016 22:22, Christian Mauderer wrote:
>>
On 29/04/2016 16:19, Christian Mauderer wrote:
Am 29.04.2016 um 02:45 schrieb Chris Johns:
On 28/04/2016 18:27, Christian Mauderer wrote:
Am 27.04.2016 um 02:07 schrieb Chris Johns:
On 26/04/2016 22:22, Christian Mauderer wrote:
Am 26.04.2016 um 04:51 schrieb Chris Johns:
On 26/04/2016 07:22
Am 29.04.2016 um 02:45 schrieb Chris Johns:
> On 28/04/2016 18:27, Christian Mauderer wrote:
>> Am 27.04.2016 um 02:07 schrieb Chris Johns:
>>> On 26/04/2016 22:22, Christian Mauderer wrote:
Am 26.04.2016 um 04:51 schrieb Chris Johns:
> On 26/04/2016 07:22, Joel Sherrill wrote:
>>
>> I
On 28/04/2016 18:27, Christian Mauderer wrote:
Am 27.04.2016 um 02:07 schrieb Chris Johns:
On 26/04/2016 22:22, Christian Mauderer wrote:
Am 26.04.2016 um 04:51 schrieb Chris Johns:
On 26/04/2016 07:22, Joel Sherrill wrote:
I put some work into building civetweb using RSB. My configuration
Am 27.04.2016 um 02:07 schrieb Chris Johns:
> On 26/04/2016 22:22, Christian Mauderer wrote:
>> Am 26.04.2016 um 04:51 schrieb Chris Johns:
>>> On 26/04/2016 07:22, Joel Sherrill wrote:
[removed part not relevant for this part of the discussion]
>>
>> 2. Currently there
On 26/04/2016 22:22, Christian Mauderer wrote:
Am 26.04.2016 um 04:51 schrieb Chris Johns:
On 26/04/2016 07:22, Joel Sherrill wrote:
Agreed 100%!
NTP has an RSB recipe and there are others for various libraries which
should be good examples. Shouldn't take long to do the recipe. Just ask
quest
Am 26.04.2016 um 04:51 schrieb Chris Johns:
> On 26/04/2016 07:22, Joel Sherrill wrote:
>> Agreed 100%!
>>
>> NTP has an RSB recipe and there are others for various libraries which
>> should be good examples. Shouldn't take long to do the recipe. Just ask
>> questions rather than getting stuck.
>>
On 26/04/2016 07:22, Joel Sherrill wrote:
Agreed 100%!
NTP has an RSB recipe and there are others for various libraries which
should be good examples. Shouldn't take long to do the recipe. Just ask
questions rather than getting stuck.
On Apr 25, 2016 7:03 PM, "Gedare Bloom" mailto:ged...@rtems.
Agreed 100%!
NTP has an RSB recipe and there are others for various libraries which
should be good examples. Shouldn't take long to do the recipe. Just ask
questions rather than getting stuck.
On Apr 25, 2016 7:03 PM, "Gedare Bloom" wrote:
> On Mon, Apr 25, 2016 at 11:25 AM, Joel Sherrill wrote
On Mon, Apr 25, 2016 at 11:25 AM, Joel Sherrill wrote:
>
>
> On Mon, Apr 25, 2016 at 4:22 AM, Christian Mauderer
> wrote:
>>
>> Essentially I agree that it would be nice to build civetweb as an
>> external library especially with the different network stacks in mind.
>> But there are some points
On Mon, Apr 25, 2016 at 4:22 AM, Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:
> Essentially I agree that it would be nice to build civetweb as an
> external library especially with the different network stacks in mind.
> But there are some points that keep me from doing it:
>
Essentially I agree that it would be nice to build civetweb as an
external library especially with the different network stacks in mind.
But there are some points that keep me from doing it:
1. I have really no Idea what would be necessary to build it as an
upstream project using RSB. If that are
I am really with Gedare and Chris that it would be better to treat this as
an upstream project. Use the RSB and track patches through RTEMS tools.
It would be a good case to push the model of a single network service
supporting both stacks and begin the process of removing networking code
from the
I think patch 05/13 probably adds civetweb.c and civetweb.h? But it
did not come through the mailman.
On Thu, Apr 21, 2016 at 4:46 PM, Gedare Bloom wrote:
> P.S. might be worth it to open a ticket related to civetweb and
> #update it from these patches.
>
> On Thu, Apr 21, 2016 at 4:45 PM, Gedare
On 22/04/2016 15:04, Christian Mauderer wrote:
> And yes: The patch didn't get through. I have got a replay that "Your
> message to devel awaits moderator approval". The civetweb.c file is over
> 300k and the mailing list seems to have a maximum of 256k.
The patch is 437875 bytes and is larger tha
P.S. might be worth it to open a ticket related to civetweb and
#update it from these patches.
On Thu, Apr 21, 2016 at 4:45 PM, Gedare Bloom wrote:
> Is the plan eventually to be able to use the upstream civetweb? or to
> track it with our own copy?
>
> On Thu, Apr 21, 2016 at 4:49 AM, Christian
Is the plan eventually to be able to use the upstream civetweb? or to
track it with our own copy?
On Thu, Apr 21, 2016 at 4:49 AM, Christian Mauderer
wrote:
> This patch series replaces the mongoose webserver by its still MIT
> licensed fork civetweb.
>
> Please note that I try to get some (curre
Yes that's right. 05/13 just adds the unchanged sources from civetweb.
Beneath civetweb.c and civetweb.h it also adds handle_form.inl and
md5.inl. The last two files are included into civetweb.c. According to
the documentation "The *INL* file extension represents code that is
statically included in
On Thu, Apr 21, 2016 at 7:36 PM, Chris Johns wrote:
> On 21/04/2016 18:49, Christian Mauderer wrote:
>
>> This patch series replaces the mongoose webserver by its still MIT
>> licensed fork civetweb.
>>
>> Please note that I try to get some (currently two) of the patches
>> directly into civetweb
On 21/04/2016 18:49, Christian Mauderer wrote:
This patch series replaces the mongoose webserver by its still MIT
licensed fork civetweb.
Please note that I try to get some (currently two) of the patches
directly into civetweb too. But I think that it might need some time and
adaption till they
This patch series replaces the mongoose webserver by its still MIT
licensed fork civetweb.
Please note that I try to get some (currently two) of the patches
directly into civetweb too. But I think that it might need some time and
adaption till they are accepted. So I thought that adding them to RT
25 matches
Mail list logo
