Re: civetweb upstream

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Feb 6, 2015 at 8:02 PM, Yehuda Sadeh-Weinraub <yehuda@xxxxxxxxxx> wrote:
>
>
> ----- Original Message -----
>> From: "Ken Dreyer" <kdreyer@xxxxxxxxxx>
>> To: ceph-devel@xxxxxxxxxxxxxxx
>> 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@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux