All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Pete Zaitcev <zaitcev@redhat.com>,
	Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: Nathan Cutler <ncutler@suse.cz>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: civetweb upstream/downstream divergence
Date: Fri, 30 Oct 2015 17:00:01 +0900	[thread overview]
Message-ID: <56332381.4060204@dachary.org> (raw)
In-Reply-To: <20151029225738.51b8b2e5@lembas.zaitcev.lan>

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hi Pete,

On 30/10/2015 13:57, Pete Zaitcev wrote:
> On Thu, 29 Oct 2015 10:58:07 -0700
> Yehuda Sadeh-Weinraub <yehuda@redhat.com> wrote:
> 
>> We should definitely do it. We're based off civetweb 1.6, and there
>> was no official civetweb version for quite a while, but 1.7 was tagged
>> a few months ago. I made some effort and got most of our material
>> changes upstream, however, there are some changes that might need some
>> more work before we can get them merged, or might not make complete
>> sense at all.
> 
> I take it Nathan is volunteering to parse the delta into logical pieces
> and identify what upstream is willing to accept, right?

I've discussed with Nathan about this general problem a few times. The issue is much less about volunteering and much more about how to track the progress of the delta over time.

> Dunno about SuSE, but as a Fedora packager I would prefer if we (Ceph)
> talked upstream into making regular releases and then for us to stop
> carrying it entirely. One less git submodule if nothing else.

Right now we have no method. For the jerasure / gf-complete sub-modules, I'm watching the delta and do the right thing but it's mostly an unwritten process: someone else would do it completely differently. For other Ceph sub-modules I suppose each developer has his own way of dealing with the delta.I remember Sage recently proposed patches upstream for rocksdb but I'm unaware of where or how. I would not be able to help him in any way. And I don't think anyone could figure out exactly how to deal with the jerasure / gf-complete sub-modules either.

Do you happen to know a project that is using submodules (or copies of projects instead of dependencies) and that is also well organized to track the delta ?

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-10-30  8:00 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 [this message]
2015-10-30 21:38     ` Ken Dreyer
2015-11-02 17:47       ` Martin Millnert
2015-11-03  9:22         ` Nathan Cutler
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=56332381.4060204@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ncutler@suse.cz \
    --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.