Re: Checking out orphans with -f

From: Martin Fick <mfick@codeaurora.org>
Date: Jan 18, 2012, 22:45 UTC
Message-ID: <201201181545.30043.mfick@codeaurora.org>
In-Reply-To: <7vsjjcljmj.fsf@alter.siamese.dyndns.org>

On Wednesday, January 18, 2012 03:40:36 pm Junio C Hamano wrote:

Show 16 quoted lines

> Martin Fick <mfick@codeaurora.org> writes:
> > I am trying to write some scripts which do various
> > things to a git repo and I have run into a issue where
> > I think that git behavior with respect to orphan
> > branches is potentially
> > 
> > undesirable.  If I type:
> >   git checkout --orphan a
> > 
> > I cannot easily abandon this state
> 
> What do you mean by "abandon"?
> 
> If you want to remove a branch "a" because you do not
> need it, you can check out some other branch and say
> "git branch -D a", no?

By abandon, I simply mean to check out another branch, which as you point, I can almost do. I just can't do it by checking out another orphaned branch! Why not, this seems inconsistent? In both cases I loose what the original orphaned branch (a) is, so why prevent me from doing it in the one case and not the other?

-Martin

-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum