Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge back into upstream LibLaserCut #41

Open
mgmax opened this issue Jun 20, 2019 · 5 comments
Open

Merge back into upstream LibLaserCut #41

mgmax opened this issue Jun 20, 2019 · 5 comments

Comments

@mgmax
Copy link

mgmax commented Jun 20, 2019

Hi @kkaempf @jnweiger ,
It would be great to have your thunderlaser driver merged back into the main VisiCut/LibLaserCut version. Then, you could just use that version and profit from the recent improvements.

@jnweiger
Copy link
Member

That would be great.
The tricky part is to find some consistent start combination of VisiCut and LibLaserCut that we should submit. I have spent some time on trying to pull latest changes from t-oster into some branches, but something went wrong and I lost track. My current checkout is somehow stuck.

@mgmax
Copy link
Author

mgmax commented Nov 9, 2019

It looks as if your current LibLaserCut branch could be cleanly merged back into upstream. There will be some larger changes to LibLaserCut sooner or later, maybe you want to use the chance to merge now? :-)

@sebastian-schmid
Copy link

Is there already a merge request in work?

@kkaempf
Copy link
Collaborator

kkaempf commented Aug 30, 2021

Sorry, no, as I have no access to a Lasercutter due to covid restrictions. :-(

@sebastian-schmid
Copy link

Ok, I set up a development environment for VisiCut and LibLaserCut and will try to get it work. Let's see how far I can get.

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

No branches or pull requests

4 participants