{"push_id":633778036,"size":5,"distinct_size":5,"ref":"refs/heads/master","head":"4fd0053348bbc2efcc26a3ac2b5de8f537c49a97","before":"886601230bbc5ecfb61f8ed70efe2eb444d6db59","commits":[{"sha":"65c63b0a8ef504dcd3ff4c4e1e1d3e3f48db8740","author":{"email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com","name":"Sean Hefty"},"message":"fabric: Change fi_connreq_t to fid_t\n\nReplace the connection request data type to be a generic fid.\nThis will make its use more generic and allow the fi_info\nconnreq field to be use for other purposes.\n\nSigned-off-by: Sean Hefty <sean.hefty@intel.com>","distinct":true,"url":"https://api.github.com/repos/ofiwg/libfabric/commits/65c63b0a8ef504dcd3ff4c4e1e1d3e3f48db8740"},{"sha":"09b9fc7ab2c0f7cc98f1d14916e5f6c07531c2b1","author":{"email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com","name":"Sean Hefty"},"message":"fabric: Define connreq handle type\n\nThe fi_info handle will support multiple types of handles.\nCurrently only a connreq type is supported.  In order to\nsupport other types, define a connreq handle type, and\nupdate the providers to set the type.\n\nSigned-off-by: Sean Hefty <sean.hefty@intel.com>","distinct":true,"url":"https://api.github.com/repos/ofiwg/libfabric/commits/09b9fc7ab2c0f7cc98f1d14916e5f6c07531c2b1"},{"sha":"5c0cec0f275666e71e8484939ca783e7f1bc5882","author":{"email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com","name":"Sean Hefty"},"message":"fabric: Add setname functionality to endpoint ops\n\nIn order to support sockets over OFI, we need to allow an application\nto associate an address with an EP after it has been created.\n\nSigned-off-by: Sean Hefty <sean.hefty@intel.com>","distinct":true,"url":"https://api.github.com/repos/ofiwg/libfabric/commits/5c0cec0f275666e71e8484939ca783e7f1bc5882"},{"sha":"f82a63224ca13838c1bc51cf60b4964a6378c2c2","author":{"email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com","name":"Sean Hefty"},"message":"fabric: Allow an active endpoint to inherit properties of a passive EP\n\nTo support sockets, we need a mechanism to reserved transport and\nnetworking addresses that can be used either on the active or passive\nside of a connection.  Expand the definition of a passive endpoint\nto support this concept.  A passive endpoint may be assigned an\naddress, which is later transferred to an active endpoint using the\nfi_info handle field.  Conceptually, the passive EP is 'converted'\ninto an active EP.  The active EP inherits all the properties that\nhave been set for the passive EP.\n\nSigned-off-by: Sean Hefty <sean.hefty@intel.com>","distinct":true,"url":"https://api.github.com/repos/ofiwg/libfabric/commits/f82a63224ca13838c1bc51cf60b4964a6378c2c2"},{"sha":"4fd0053348bbc2efcc26a3ac2b5de8f537c49a97","author":{"email":"9575f92314b8ac7581ac1b2afb880058b7fbd431@intel.com","name":"Sean Hefty"},"message":"Merge pull request #900 from shefty/master\n\nEnhance support for sockets over OFI","distinct":true,"url":"https://api.github.com/repos/ofiwg/libfabric/commits/4fd0053348bbc2efcc26a3ac2b5de8f537c49a97"}]}