Am 17.12.23 um 23:29 schrieb andy pugh:
On Sun, 17 Dec 2023 at 21:40, Hans Unzner wrote:
If you think the files are generated correctly, you should commit them.
They probably are, but how would I tell?
Take some random samples maybe? Or you can open a pull request for this...
Am 17.12.23 um 22:37 schrieb Hans Unzner:
Am 17.12.23 um 11:17 schrieb andy pugh:
When I do test builds on my local machine I seem to create new .po and
,pot files.
These show up as uncommitted changes in Git, and prevent rebasing etc.
What is the right thing to do with these?
It seems
On Sun, 17 Dec 2023 at 21:40, Hans Unzner wrote:
> If you think the files are generated correctly, you should commit them.
They probably are, but how would I tell?
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses,
Am 17.12.23 um 11:17 schrieb andy pugh:
When I do test builds on my local machine I seem to create new .po and
,pot files.
These show up as uncommitted changes in Git, and prevent rebasing etc.
What is the right thing to do with these?
It seems that the target 'pofiles' have been invoked,
Processing commands for cont...@bugs.debian.org:
> found 1053251 2.9.0~pre1+git20230208.f1270d6ed7-1
Bug #1053251 {Done: Sebastian Ramacher }
[linuxcnc-uspace] linuxcnc-uspace: Uncommanded axis movement in MDI mode with
some UIs
Marked as found in versions
When I do test builds on my local machine I seem to create new .po and
,pot files.
These show up as uncommitted changes in Git, and prevent rebasing etc.
What is the right thing to do with these?
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial
