Re: `git checkout --orpan` leaves a dirty worktree
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 8, 2013, 20:12 UTC
- Message-ID
- <7vzjzezhrr.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20130208200402.GB8461@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 20 quoted lines
> 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. :)
So true ;-).
Especially when you may an answer that may make _you_ look like an idiot ;-)