On 1 June 2010 04:02, Josh Allmann <[email protected]> wrote: > On 31 May 2010 14:56, Mohamed Naufal <[email protected]> wrote: >> On 1 June 2010 00:04, Josh Allmann <[email protected]> wrote: >>> On 31 May 2010 10:49, Martin Storsjö <[email protected]> wrote: >>>>> >>>>> > 3) if you don't yet have a SVN account for our summer-of-code >>>>> > repository, please reply to this email so we can fix that >>>>> >>>>> >>>>> /me needs one >>>> >>>> Does it have to be in form of a patch-repo under ffmpeg-soc for formal >>>> reasons, or would it count just as well if it was available as a git repo >>>> somewhere? Then it wouldn't be on our formal servers, but I think the >>>> development as such would be smoother there. >>> >>> We can try working from this: >>> [email protected]:j0sh/ffmpeg-soc.git >>> (http://github.com/j0sh/ffmpeg-soc) >>> >>> Still trying to figure out the commit hook for the ffmpeg-soc ML though. >>> >> >> >> Github doesn't support inclusion of diff contents in commit >> notification mails. An alternative: setup a local repo and configure >> the post-receive hook to send notifications to the ffmpeg-soc ml, then >> push to both the local repo as well as github. Roundabout, I admit. Do >> tell me if you figure out a better way. >> > > Github has post-recive hooks too, and I can run a sinatra instance on > my vps to handle those. Then we can send out a mail to ffmpeg-soc > formatted to our heart's content. > > we can get a diff by appending '.patch' to the end of the commit urls > in the github payload. > (http://github.com/github/github-services/blob/master/docs/github_payload) >
That is even geekier ;) [...] Regards Naufal _______________________________________________ FFmpeg-soc mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
