Skip to content

Conversation

porlock
Copy link

@porlock porlock commented Dec 5, 2019

Requirements

Fixing bugs

Description

Benefits

Fixing bugs

Related Issues

none

@thinkyhead thinkyhead force-pushed the 2.0.x branch 2 times, most recently from a5e94a2 to 5103cdc Compare December 6, 2019 02:05
@inib
Copy link
Owner

inib commented Dec 6, 2019

I'll go for a restructure on the branches on Sunday.
sorry for the delay, but I currently have very little spare time.

@thinkyhead thinkyhead force-pushed the 2.0.x branch 4 times, most recently from 4783282 to 432decd Compare December 25, 2019 21:09
@thinkyhead thinkyhead force-pushed the 2.0.x branch 3 times, most recently from 5de74e6 to ccdeb3f Compare January 13, 2020 22:50
@thinkyhead thinkyhead force-pushed the 2.0.x branch 7 times, most recently from 8eb6603 to e6a7be9 Compare January 31, 2020 10:29
@thinkyhead thinkyhead force-pushed the 2.0.x branch 5 times, most recently from 193f1fd to d6e767e Compare February 27, 2020 10:15
@thinkyhead thinkyhead force-pushed the 2.0.x branch 4 times, most recently from 36bab2b to 015c4e6 Compare March 31, 2020 19:45
@iamkarlson
Copy link

whoa too many commits in here. @thinkyhead you're doing great stuff! did you test it on your machine? I see that you merged a lot of code from marlin repo but how stable is it? would you recommend code from this pull request for daily usage?

@thinkyhead
Copy link

The commits you see are not specifically recent, but are just a quirk of GitHub in the way it shows PRs that don't really fit together. Merge or rebase should be done between the relevant branches within your own workspaces, pulling from the various remotes as needed.

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.