SZEDER Gábor <sze...@ira.uka.de> writes: > git-sh-setup's require_clean_work_tree() always exits with error on an > orphan branch, even when the index and worktree are both clean.
Ah, I just sent a review on 1/2 as I found it was not commented on by anybody, but re-reading this sentence (and subsequent review of this 2/2) makes it clear this is not a good idea. By definition, the index immediately after creating and getting on an orphan branch is not clean [*1*]. I'll move the topic from "Needs review" to "Will discard" pile in my tree. Sorry for the noise. [Footnote] *1* Roughly speaking, if "git commit" (no arguments) to record the state of the index succeeds without "--allow-empty", your index is dirty with respect to HEAD. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
