Fork a subset of a repo – licensing and etiquette
I’m a contributor to a large open source project. I have made heavy changes to a submodule of that project to support more functionality, but at this point further improvements will be outside the scope of the original project. As such, I have pulled only the relevant files to the submodule into their own repo, and am proceeding with a major rewrite to allow for these new features. The file structure is such that this submodule can live on it’s own, with the original as a dependency.
Fork a subset of a repo – licensing and etiquette
I’m a contributor to a large open source project. I have made heavy changes to a submodule of that project to support more functionality, but at this point further improvements will be outside the scope of the original project. As such, I have pulled only the relevant files to the submodule into their own repo, and am proceeding with a major rewrite to allow for these new features. The file structure is such that this submodule can live on it’s own, with the original as a dependency.
forking but not exiting
It is normal for the child in a fork() to call exec() or _exit().
forking but not exiting
It is normal for the child in a fork() to call exec() or _exit().
forking but not exiting
It is normal for the child in a fork() to call exec() or _exit().