> -----Original Message----- > From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel- > owner@xxxxxxxxxxxxxxx] On Behalf Of Loic Dachary > Sent: Tuesday, June 13, 2017 8:52 AM > To: Mahalingam, Ganesh <ganesh.mahalingam@xxxxxxxxx> > Cc: Gohad, Tushar <tushar.gohad@xxxxxxxxx>; Ceph Development <ceph- > devel@xxxxxxxxxxxxxxx> > Subject: Re: Ceph ISA-L git submodule > > [cc'ing ceph-devel] > > Hi ! > > On 06/13/2017 05:25 PM, Mahalingam, Ganesh wrote: > > Hi Loic, > > Apologies for the duplicate communication. Just thought leaving an > > email would be better compared to trusting the persistence of IRC. :) > > > > Was wondering if you could shed some light on how the community handles > submodule updates? Does the maintainer get the latest from the upstream > project and then a PR will just change the SHA reference or do we do a PR to > the submodule as well? > > Yes, it's basically how it is done. [Mahalingam, Ganesh] Thanks Loic. if I understand this as the maintainer updated the ceph copy, might I put in a request to update the ceph fork of isa-l? > > > We wanted to update the ISA-L sources from v2.16 to v2.18 and hence the > questions. > > The automated make check will use the new submodule to verify it is able to > decode/encode shards. [Mahalingam, Ganesh] Awesome. Thanks for the info. > > Cheers > > -- > Loïc Dachary, Artisan Logiciel Libre > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the > body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
