Yeah - I didn't have any clear ideas (other than simply not sending these...), which is why I asked. > On May 21, 2018, at 4:32 PM, Andrew Hanushevsky <[log in to unmask]> wrote: > > Hi Brian, > > No, we don't have current plans as this is not an emininet problem, though getting there. I suppose we'll either have to run a webhook microserver or, assuming we can get enough free time on Google Cloud or AWS, a FaaS implementation. Either way it's pretty straight forward. Do you have something like that already? > > Andy > > On Mon, 21 May 2018, Brian Bockelman wrote: > >>> On May 16, 2018, at 9:54 PM, Andrew Hanushevsky <[log in to unmask]> wrote: >>> >>> Branch: refs/heads/master >>> Home: https://github.com/xrootd/xrootd >>> Commit: 5600997b9de24f987bb0f3a41bc9a8bfe33516cc >>> https://github.com/xrootd/xrootd/commit/5600997b9de24f987bb0f3a41bc9a8bfe33516cc >>> Author: Andrew Hanushevsky <[log in to unmask]> >>> Date: 2018-05-16 (Wed, 16 May 2018) >>> >>> Changed paths: >>> M src/XrdOuc/XrdOucCache2.hh >>> >>> Log Message: >>> ----------- >>> [Proxy] Make LocalFilePath() a bit more smart. >>> >>> >>> >>> **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ >>> >>> Functionality will be removed from GitHub.com on January 31st, 2019. >>> >> >> Hi all, >> >> This email integration is going away, right? Do we have a replacement planned? >> >> Honestly, I just use the normal github notification mechanism to get all the emails I could ever want... >> >> Brian >> ######################################################################## >> Use REPLY-ALL to reply to list >> >> To unsubscribe from the XROOTD-DEV list, click the following link: >> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1 >> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1