Vasilii, Great that you come with a typo fixing PR, thank you!
Taking a random spot-check when trying to improve our capability to work with contributors, I was particularly amenable to your contribution – as fixing typos is easy enough. I have the following review notes – perhaps you can use them already when you supply your PR? -If the changes are not amenable to automated testing, please explain why not and carefully describe how to test manually. +If the changes are not amendable to automated testing, please explain why not and carefully describe how to test manually. Nope, "amenable" is the correct, intended word. But we want "easy" words (not likely to be misunderstood). So I suggest: amen(d)able -> suitable +# * Accessebility Check # Accessebility -> Accessibility + Check a file or path for accessebility. Accessebility -> Accessibility + conversion is garanteed to be less than 251, which occupies garanteed -> guaranteed + /* wsrep_sst_*.sh scripts requite ipv6 addresses to be in square breackets */ breackets -> brackets Then for the "non-English" texts. They are in Swedish, my native tongue. Here are the proper translations -Speciella användbara nya string-rutiner: +Speciella anv�ndbara nya string-rutiner: Special, useful new string routines: - - Används istället för ctype.h för att klara internationella karakterer. + - Anv�nds ist�llet f�r ctype.h f�r att klara internationella karakterer. Is used instead of ctype.h to handle international characters - Använd instället för string.h för att supporta snabbare strängfunktioner. + Anv�nd inst�llet f�r string.h f�r att supporta snabbare str�ngfunktioner. Use instead of string.h to support faster string functions - - Använd inte strcat, använd strmov (se ovan). + - Anv�nd inte strcat, anv�nd strmov (se ovan). Do not use strcat, use strmov (see above) Kaj Den ons 19 feb. 2025 kl 19:06 skrev Sergey Vojtovich via discuss < [email protected]>: > Vasilii, > > Well, there's no doubt it is going to be a big change, at the same time > very easy to review. > Looking at your patch, the only thing that I was doubtful about were > non-english changes. > You can start with fixing C/C++ comments, files under mysql-test should > probably go separately, > then non-english changes, then error messages/etc. That is 3-4 pull > requests. > > Regards, > Sergey > > On Wed, Feb 19, 2025 at 9:01 PM Vasilii Lakhin <[email protected]> wrote: > >> Greetings, Sergey! >> >> Before I create a pull request, I want to ask how it would be convenient >> to interact (I estimate around 1000 words to be changed): >> 1. I'll make small patches (one alphabet letter at a time or 50 words at >> a time) and create PR for each take separately; >> 2. I'll make exact same patches, but with one PR; >> 3. One big patch, one PR? >> >> I'm concerned about: >> 1. Checking a single patch will be too much of a hassle; >> 2. Approving each PR will be a hassle as well. >> >> Or maybe there are better options that I don't know about. >> Thank you for response. >> >> Best regards, >> Vasilii >> >> 19.02.2025 17:00, Sergey Vojtovich wrote: >> >> Hi Vasilii, >> >> Yes, please go ahead and create pull request against "main" branch. >> https://github.com/MariaDB/server/pulls >> >> Regards, >> Sergey >> >> On Sat, Feb 15, 2025 at 5:18 PM Lakhin Vasilii via discuss < >> [email protected]> wrote: >> >>> Forgot to attach the patch I mentioned. >>> _______________________________________________ >>> discuss mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> >> _______________________________________________ > discuss mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Kaj Arnö, CEO MariaDB Foundation | @mariadb_org | +358-45-1589296 | @kajarno
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
