[openstack-dev] [all] what do you work on upstream of OpenStack?

Jay Faulkner jay at jvf.cc
Tue Jun 14 17:47:47 UTC 2016

I committed a small change to systemd-nspawn to ensure kernel modules 
could be loaded by IPA hardware managers in an older version of our 
CoreOS-based ramdisk (note that we don't use systemd-nspawn anymore, but 
instead use a chroot inside the CoreOS ramdisk).

Jay Faulkner

On 6/13/16 12:11 PM, Doug Hellmann wrote:
> I'm trying to pull together some information about contributions
> that OpenStack community members have made *upstream* of OpenStack,
> via code, docs, bug reports, or anything else to dependencies that
> we have.
> If you've made a contribution of that sort, I would appreciate a
> quick note.  Please reply off-list, there's no need to spam everyone,
> and I'll post the summary if folks want to see it.
> Thanks,
> Doug
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list