From: Nathan Cutler <ncutler@suse.cz>
To: Martin Millnert <martin@millnert.se>, Ken Dreyer <kdreyer@redhat.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Yehuda Sadeh-Weinraub <yehuda@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: civetweb upstream/downstream divergence
Date: Tue, 3 Nov 2015 10:22:37 +0100 [thread overview]
Message-ID: <56387CDD.9070605@suse.cz> (raw)
In-Reply-To: <1446486438.12033.24.camel@millnert.se>
IMHO the first step should be to get rid of the evil submodule. Arguably
the most direct path leading to this goal is to simply package up the
downstream civetweb (i.e. 1.6 plus all the downstream patches) for all
the supported distros. The resulting package would be Ceph-specific,
obviously, so it could be called "civetweb-ceph".
Like Ken says, the upstreaming effort can continue in parallel.
After we get Ceph/RGW working fine with civetweb-ceph 1.6, we can rebase
the package to upstream civetweb 1.7.
I am not volunteering to do all the work, but we at SUSE are certainly
prepared to shoulder our share of it.
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2015-11-03 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 9:19 civetweb upstream/downstream divergence Nathan Cutler
2015-10-29 10:11 ` Wido den Hollander
2015-10-29 16:56 ` Loic Dachary
2015-10-29 17:58 ` Yehuda Sadeh-Weinraub
2015-10-30 4:57 ` Pete Zaitcev
2015-10-30 8:00 ` Loic Dachary
2015-10-30 21:38 ` Ken Dreyer
2015-11-02 17:47 ` Martin Millnert
2015-11-03 9:22 ` Nathan Cutler [this message]
2015-11-03 11:22 ` Sage Weil
2015-11-04 20:25 ` Ken Dreyer
2015-11-04 23:43 ` Ken Dreyer
2015-11-04 23:54 ` Sage Weil
2015-11-05 0:04 ` Martin Millnert
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=56387CDD.9070605@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.com \
--cc=martin@millnert.se \
--cc=yehuda@redhat.com \
--cc=zaitcev@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.