From: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
To: Ken Dreyer <kdreyer@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: civetweb upstream
Date: Fri, 6 Feb 2015 12:02:53 -0500 (EST) [thread overview]
Message-ID: <391658056.205926.1423242173510.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <54D4DDAE.50604@redhat.com>
----- 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
next prev parent reply other threads:[~2015-02-06 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 15:28 civetweb upstream Ken Dreyer
2015-02-06 17:02 ` Yehuda Sadeh-Weinraub [this message]
2015-02-08 7:54 ` Mustafa Muhammad
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=391658056.205926.1423242173510.JavaMail.zimbra@redhat.com \
--to=yehuda@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.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 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.