Skip to content

Conversation

@chruoss
Copy link

@chruoss chruoss commented Oct 29, 2025

Renamed L6009.php -> L4736.php
Renamed L6009_A.php -> L4736_A.php
Added correct L6009.php
Added correct L6009_A.php

L6009

Renamed L6009_A.php -> L4736_A.php
Added correct L6009.php
Added correct L6009_A.php
@chruoss chruoss requested a review from snipe as a code owner October 29, 2025 14:24
@snipe
Copy link
Member

snipe commented Oct 29, 2025

Hi there - thanks for this! Can you please re-target this PR to point to the develop branch, per our Contributing documentation?

You don't need to close and re-open. After you create a pull request, you can modify the base branch so that the changes in the pull request are compared against a different branch. By changing the base branch of your original pull request rather than opening a new one with the correct base branch, you’ll be able to keep valuable work and discussion.

mhuxq

Also I'm not sure what problem this is exactly solving?

Thanks!

@chruoss chruoss changed the base branch from master to develop October 30, 2025 07:04
@chruoss
Copy link
Author

chruoss commented Oct 30, 2025

I changed the brach to develop.

With the original L6009 labelformat i wasn't able to print on the L6009 Labelsheet, there was too much of a gab on the top. So i took the original L6009 and renamed it to L4736 because the testprint from akspeh1on pull request #17710 was on a L4736 labelsheet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants