#linuxcnc-devel Logs

May 03 2022

#linuxcnc-devel Calendar

01:00 AM pere: silopolis[m]: note, docs/po/documentation_es.po should be stored as es.po
01:11 AM silopolis[m]: pere: is that a requirement? That's not consistent with all the other files?
01:12 AM silopolis[m]: * pere: is that a requirement? That's not consistent with all the other files 🙁
01:12 AM pere: is is how the build system work.
01:12 AM pere: and yes, it is consistent with all the other po files.
01:17 AM -!- #linuxcnc-devel mode set to +v by ChanServ
01:47 AM -!- #linuxcnc-devel mode set to +v by ChanServ
02:09 AM silopolis[m]: ok understood, wasn't looking globally enough 🙂
02:10 AM silopolis[m]: pere: what about the numbers ?
02:10 AM pere: they look good?
02:11 AM silopolis[m]: can hardly tell... How could I know ?
02:13 AM silopolis[m]: I guess we'll really figure when we'll generate translations from them, no ?
02:15 AM pere: silopolis[m]: I compare them to the total number of strings 28118 and the number in the PO files we generated earlier. The numbers are higher than before, and a significant porsion of the total.
02:15 AM pere: I do not see the point in spending more time on improving the initial PO files, and believe we should move on to maintainence mode.
02:17 AM CaptHindsight[m]: are the numbers of downloads of LCNC as a deb package available?
02:17 AM silopolis[m]: pere: honestly, except improving English docs, and without doing actual translation, I don't see how I could improve them further
02:17 AM CaptHindsight[m]: just curious
02:18 AM silopolis[m]: CaptHindsight: maybe in Debian popcon but may not be very representative
02:20 AM pere: CaptHindsight[m]: download numbers are not available. no central download of packages in debian, so no such number is collected. <URL: https://tracker.debian.org/pkg/linuxcnc > got lots of info on the package, including popcon numbers, which is self selected reporting of installed and used packages.
02:25 AM silopolis[m]: CaptHindsight: https://qa.debian.org/popcon.php?package=linuxcnc
02:26 AM silopolis[m]: pere: fixed file names
02:26 AM pere: silopolis[m]: so, time to wrap up the po4a migration?
02:27 AM CaptHindsight[m]: thanks
02:27 AM CaptHindsight[m]: Vote (195143) Vote is the number of people who use this package regularly
02:28 AM silopolis[m]: pere: AFAIC, yes
02:31 AM pere: CaptHindsight[m]: it is collected using file stats the last week, ie machines where the package files were read the last week (excluding files read by cron jobs).
02:46 AM -!- #linuxcnc-devel mode set to +v by ChanServ
03:38 AM pere: silopolis[m]: please make sure hans is quickly made aware of our conclusion. do you have any views on the unsolved tasks in https://github.com/LinuxCNC/linuxcnc/pull/1713 ?
03:44 AM pere: seb_kuzminsky: eagerly awaiting your email answer on the norwegian visit.
03:51 AM silopolis[m]: <pere> "silopolis: please make sure hans..." <- both answered the question and tagged @hansu in last comment on #1724
03:51 AM silopolis[m]: All tasks in #1713 are completed up to 5th included by #1724
03:58 AM pere: good
04:27 AM silopolis[m]: hoped you to say that for so long, almost dropped a tear ! 😘
04:34 AM silopolis[m]: does squashing commits preserves authoring ?
05:16 AM pere: silopolis[m]: yes, depending on how it is squashed.
05:24 AM silopolis[m]: pere: how so then ? 'cause all I find on the Net are workarounds as Git doesn't support multiple authors
05:26 AM silopolis[m]: Best option I found would be to set myself as commiter only, preserve one author and add others into "Co-authored by: " trailers in commit messages
05:48 AM pere: silopolis[m]: try for yourself by doing 'git checkout -b mytestbranch; git rebase -i master'. :)
05:52 AM pere: Note, I do not propose to squash all commits into one, just reduce the number of commits to logically units
06:02 AM pere: I just tested myself, and sadly the adoc files have been changed both in master and in your branch, causing merge conflicts.
06:03 AM pere: the effect is that it will take more time than I have available now to get this branch into master.
06:16 AM silopolis[m]: pere: I'll do it
06:16 AM pere: silopolis[m]: perhaps better to let hans merge your branch into docs-devel first, to avoid having to do it twice?
06:23 AM silopolis[m]: I can rebase my branch on master too
06:28 AM pere: sure, but that will just make it harder to get it into docs-devel, and still the merge conflict would have to be resolved again....
06:28 AM pere: you could rebase and squash it on top of docs-devel. I suspect that might be helpful, but check with hans.
11:32 AM silopolis[m]: pff, than rebasing is giving me hard times 😕
03:08 PM Tom_itx is now known as Tom_L