Hi, Am 26.07.2018 um 15:53 schrieb FR web forum: > Thanks for this answer > I know that I can do it with SVN > But this is too heavy for me to download all aoo-trunk files. > Is it possible to create a patch from Github and then submit to BZ?
I don't know. But since it is only two lines, I will include it in my next build and everyone can test it. Regards, Matthias > > ----- Mail original ----- >> De: "Matthias Seidel" <matthias.sei...@hamburg.de> >> À: dev@openoffice.apache.org >> Envoyé: Jeudi 26 Juillet 2018 11:31:35 >> Objet: Re: Patch through Github >> >> Hi, >> >> I think GitHub is "readonly". >> >> Contributions can be made with subversion: >> https://openoffice.apache.org/source.html >> https://openoffice.apache.org/contributing-code.html >> >> Or you can attach a patch file to the specific issue in Bugzilla. >> >> Did you test the code or would you be interested in a special >> (Windows) >> build? >> I don't have such a fancy mouse... ;-) >> >> Regards, >> >> Matthias >> >> Am 26.07.2018 um 11:21 schrieb FR web forum: >>> Hello dev team, >>> Is it a right way to submit patch through Github? >>> https://github.com/apache/openoffice/pulls >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
