-
Notifications
You must be signed in to change notification settings - Fork 13
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
Would you accept merging development with the dillo-browser fork? #21
Comments
This could be nice. At the moment i'm trying to remove all uneeded dependencies from the project. Let me review the code of the other repo and see if a merge if possible. Otherwise, if our objectives are different, I'm open to periodically exchange patches to improve both projects |
Let me explain: my targets are also BSD and (some) embedded systems. So my code can not be too much Linux centered. This may lead to different devop procedures, but exchanging functionalities and patches is always possible (and welcome too) |
That sounds great! I agree that it can only improve code quality if multiple CI pipelines would be hooked up to verify compilation and run tests on major platforms (TODO: enumerate) and CD pipelines to assemble binaries as well. |
code should be portable between unix-likes, the fact not everyone uses linux, helps ensure that linux-specific stuff doesn't sneak in and break compatibility with other systems, one of the strengths of dillo is that it can easily be compiled for a ton of different systems ;) |
dillo-browser/dillo#53 (comment)
You seem to have a common goal, so why not converge the source so patches could be shared or even a single repository could be used?
The text was updated successfully, but these errors were encountered: