On Fri, Jan 27, 2017 at 11:52:34AM +0200, Otto Kekäläinen wrote: > Thanks Julian, you've done a very thorough job in producing and > documenting the patch. > > In future, if you send a patch, please do it as public git branches so > I can easily pull (and you can easily rebase when the target repo > updates). Or alternatively you can send patches on Github as pull > requests. > Git: https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/ > (mirror https://github.com/ottok/mariadb-10.1)
OK, I'll make a branch. Ah, have done, but of course I don't have write-access to the pkg-mysql repository to create it. How can I make a public branch on alioth? Anyhow, I've just made a fork on github and created a pull request there. > I am a bit afraid of applying this patch, as we are quite late in the > release cycle, and I already did this week extensive jessie->stretch > tests this week and I didn't come across any issues. Applying new > patches to the maintainer scripts seems a bit risky as there could be > some severe unintentional regressions. Also, because doing so much > testing I am quite worn out right now and afraid of making mistakes > simply because of being tired. Indeed; I do appreciate this. I don't know what others think - could/should this wait for the next release cycle? > Is there anybody on the pkg-maint-mysql team that could step in here, > review the patch as such, and maybe even apply it on a test branch, > build, and do some testing? :-) Best wishes, Julian
