3 ms·
PWNO provided a patch but it was rejected for being too large[1]. A maintainer fixed it himself[2]. I don't know if PWNO used a LLM but it seems clear that the
by tredre3 10mo ago
PWNO provided a patch but it was rejected for being too large[1]. A maintainer fixed it himself[2]. I don't know if PWNO used a LLM but it seems clear that the maintainer had a preferred specific style in mind so it was likely hand written (albeit inspired by the initial patch).
1. https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21258 https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21258
2. https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/4bfac71ecd96488dd2dcd5649e08edb039a17a8b https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/4bfac71ecd96488...
- j1elo 10mo agoI just need to say that "commits" has been translated to Spanish as "confirmations" in that website, and it made me chuckle. Is Forgejo using LLM-assisted translations? Or simply somepne without any context whatsoever in order to understand the word's meaning? ---- EDIT: I went on a fun detour to inform myself better, and ended up finding [1] where Gitlab had the same discussion. Seems some translations have tried to use "confirmation" as translation for a git commit. But really, this is one of those cases where no local word is able to appropriately describe such an unique concept oridea. I'd love to retroactively chime in and confirm (hah) that the english word "Commit" has trascended any translation attempts, and absolutely nobody would know what you're talking about if you say "confirmation" in an attempt to use a spanish term. So Forgejo authors if you read this: it'd better to do as Gitlab did. [1]: https://gitlab.com/gitlab-org/gitlab/-/issues/215956 https://gitlab.com/gitlab-org/gitlab/-/issues/215956