On Wed, Jun 29, 2016 at 02:15:46PM -0500, Steve Wise wrote: > > I think you start by realizing that nobody uses your git releases > > anyhow. > > > > Not true. RedHat, for one, does. I mean no users. > > Everyone uses either a distro or OFED release and those are already > > co-ordinated outside your control. > > I don't know who "everyone" is, but at least some of the distros get > the everyone = users > libcxgb3/4 packages from releases I publish and announce on > linux-rdma. Chelsio recommends to RedHat exactly which libcxb > release to pull in for each of their OS releases. They are not > necessarily tied to an OFED release either. Ditto for SUSE, > although they may still take from OFED packages. And that doesn't really change, you just recommend a libibverbs release or libibverbs patch. > From what I've experienced, the distros don't take patches for > libraries at all. They take discreet releases that are published by > the maintainer of that Your view might be a bit specialized because a plugin 'library' is a very special case. Generally the distros will have tight controls on library updates to guarentee no change to the ABI/API. Often they won't accept new upstream library versions at all, instead only backporting necessary fixes. For instance, if you add the new CQ API support the libcxgb (or any new API for that matter) then the provider will no longer compile on the RH released libibverbs and either Doug will have to work on a backport basis, or you will have to jump through configure hoops to make it compile. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
