* civetweb upstream
@ 2015-02-06 15:28 Ken Dreyer
2015-02-06 17:02 ` Yehuda Sadeh-Weinraub
0 siblings, 1 reply; 3+ messages in thread
From: Ken Dreyer @ 2015-02-06 15:28 UTC (permalink / raw)
To: ceph-devel@vger.kernel.org
Hi folks,
It looks like Ceph has its own fork of the upstream civetweb project.
What was the reason for forking at the time? Has there been much effort
to get our civetweb changes upstream?
- Ken
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: civetweb upstream
2015-02-06 15:28 civetweb upstream Ken Dreyer
@ 2015-02-06 17:02 ` Yehuda Sadeh-Weinraub
2015-02-08 7:54 ` Mustafa Muhammad
0 siblings, 1 reply; 3+ messages in thread
From: Yehuda Sadeh-Weinraub @ 2015-02-06 17:02 UTC (permalink / raw)
To: Ken Dreyer; +Cc: ceph-devel
----- Original Message -----
> From: "Ken Dreyer" <kdreyer@redhat.com>
> To: ceph-devel@vger.kernel.org
> Sent: Friday, February 6, 2015 7:28:46 AM
> Subject: civetweb upstream
>
> Hi folks,
>
> It looks like Ceph has its own fork of the upstream civetweb project.
> What was the reason for forking at the time? Has there been much effort
> to get our civetweb changes upstream?
>
The biggest motivation originally was to get it integrated into our automake system, as it was using weird suffixes for some include file. When civetweb was split out of mongoose, they made some changes to the code structure that made it harder to embed into our system. Later on there were some relatively minor changes and bug fixes. We might be able to push some upstream as is, and some might need to be reworked so that they'd make sense in that context.
Yehuda
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: civetweb upstream
2015-02-06 17:02 ` Yehuda Sadeh-Weinraub
@ 2015-02-08 7:54 ` Mustafa Muhammad
0 siblings, 0 replies; 3+ messages in thread
From: Mustafa Muhammad @ 2015-02-08 7:54 UTC (permalink / raw)
To: ceph-devel
On Fri, Feb 6, 2015 at 8:02 PM, Yehuda Sadeh-Weinraub <yehuda@redhat.com> wrote:
>
>
> ----- Original Message -----
>> From: "Ken Dreyer" <kdreyer@redhat.com>
>> To: ceph-devel@vger.kernel.org
>> Sent: Friday, February 6, 2015 7:28:46 AM
>> Subject: civetweb upstream
>>
>> Hi folks,
>>
>> It looks like Ceph has its own fork of the upstream civetweb project.
>> What was the reason for forking at the time? Has there been much effort
>> to get our civetweb changes upstream?
>>
>
> The biggest motivation originally was to get it integrated into our automake system, as it was using weird suffixes for some include file. When civetweb was split out of mongoose, they made some changes to the code structure that made it harder to embed into our system. Later on there were some relatively minor changes and bug fixes. We might be able to push some upstream as is, and some might need to be reworked so that they'd make sense in that context.
>
> Yehuda
I posted on another thread about changing the upstream before reading
this, sorry about that, but I think this should be done before Hammer
release.
Regards
Mustafa
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-02-08 7:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-06 15:28 civetweb upstream Ken Dreyer
2015-02-06 17:02 ` Yehuda Sadeh-Weinraub
2015-02-08 7:54 ` Mustafa Muhammad
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.