Hello On Wed, 2018-10-17 at 17:48 +0200, Patrick Storz wrote: > Hi Michal, > thanks for the answer! > That's unfortunate. If behavior as discussed in the linked issue > would be implemented that would likely solve out issue. However I > figure it might be hard to get the re-ordering per author right?
I think it should be doable. The good news is that I'll get some funding to work on this, so it's quite likely it will be done for next release. > Without it still a lot of unnecessary commits would be produced when > two or more translators are working in parallel while a merge/rebase > is triggered. > Is there any possibility to disable calling commit_pending on > merges/rebases (possibly by patching the code) or are there technical > reasons that require Weblate to commit changes before > merging/rebasing? It has to be commited to be able to merge/rebase changes on current master. The commit could be left out if there are no changes in the translation files, what would need some introspection of incoming upstream changes. I've shortly described this in following issue: https://github.com/WeblateOrg/weblate/issues/2332 -- Michal Čihař | https://cihar.com/ | https://weblate.org/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
