Re: `git checkout --orpan` leaves a dirty worktree

Am 08.02.2013 21:17, schrieb Junio C Hamano: > Ramkumar Ramachandra writes: > >> BTW, Is there a better way to clean out the worktree than `git rm -rf >> .`, since that fails for submodules? The impulsive `reset --hard` >> obviously fails because there is no HEAD. > > I _think_ the "git rm" is

Re: `git checkout --orpan` leaves a dirty worktree

I'm curious what your use case is. The behavior has been inconvenient for me too, but I have only used it in test cases; I have no real use case where I wanted to create an unborn/orphan branch. On Fri, Feb 8, 2013 at 11:50 AM, Ramkumar Ramachandra wrote: > Hi, > > Why should I have to `git rm -

Re: `git checkout --orpan` leaves a dirty worktree

Ramkumar Ramachandra writes: > BTW, Is there a better way to clean out the worktree than `git rm -rf > .`, since that fails for submodules? The impulsive `reset --hard` > obviously fails because there is no HEAD. I _think_ the "git rm" is one of the things on Jens's roadmap. Also I think "rese

Re: `git checkout --orpan` leaves a dirty worktree

Jonathan Nieder writes: > 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

Re: `git checkout --orpan` leaves a dirty worktree

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 th