Re: `git checkout --orpan` leaves a dirty worktree
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Feb 8, 2013, 20:04 UTC
- Message-ID
- <20130208200402.GB8461@google.com>
- In-Reply-To
- <CALkWK0mjf5vsiHvMW-QyzMHdmZQvdzjw_ORJnMd=mT6RCqB1xg@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Why should I have to `git rm -rf .` after a `git checkout --orphan`? > What sort of misfeature/ incomplete feature is this?
One designed for the "going open source" use case, where you have existing code that you want to put into a new branch without history. When there is no existing code, it seems simpler to do
cd .. git init code-that-has-nothing-to-do-previous-cwd cd code-that-* ... hack hack hack ... git commit git remote add origin <url> git push -u origin master
BTW, I suspect a clearer way to say what you meant is "Sounds like a misfeature" which is gentler and more focused than an implied "What kind of idiot designed this?" Even if you are thinking the latter. :)
Hope that helps, Jonathan