Currently developing futuristic smart-device, IoT connected, highway construction site safety system in EU.
Used to work on infrastructure, application architecture and cloud engineering.
Hi, I actually found one example directly in the git man page for git-checkout:
This can be useful when you want to publish the tree from a commit without exposing its full history. You might want to do this to publish an open source branch of a project whose current tree is "clean", but whose full history contains proprietary or otherwise encumbered bits of code.
Cool, that's a great spotting! I didn't read the full piece of the git man page for the --orphan flag and now I have learned something new on top of what I wrote. Thanks for your comments!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, I actually found one example directly in the git man page for git-checkout:
This can be useful when you want to publish the tree from a commit without exposing its full history. You might want to do this to publish an open source branch of a project whose current tree is "clean", but whose full history contains proprietary or otherwise encumbered bits of code.Cool, that's a great spotting! I didn't read the full piece of the git man page for the
--orphanflag and now I have learned something new on top of what I wrote. Thanks for your comments!