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

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:56:05

Ramkumar Ramachandra [off-list ref] 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 "reset --hard" these days does know what to do when you do
not have any history yet.

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

From: Jens Lehmann <hidden>
Date: 2016-06-15 22:56:06

Am 08.02.2013 21:17, schrieb Junio C Hamano:
Ramkumar Ramachandra [off-list ref] writes:
quoted
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.
Hmm, "git rm" does remove submodules since 1.8.1 (but they have to be
cloned with Git 1.7.8 or newer). Or is there something special about
the orphan checkout I'm missing here?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help