git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Checking out orphans with -f

From
MFMartin Fick <mfick@codeaurora.org>
Date
Jan 18, 2012, 19:07 UTC
Message-ID
<201201181207.05967.mfick@codeaurora.org>

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 by simply typing:
  git check -f --orphan b

Is there a better simpler way to abandon a that I am not aware of? Am I miss understanding what -f is supposed to do? It seems like it should allow me to abandon the a orphan and continue to checkout the b orphan?

Thanks for any insights,
-Martin
-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum
Next: Junio C Hamano
Message 1 of 5 in “Checking out orphans with -f”
  1. Martin FickJan 18, 2012
  2. Junio C HamanoJan 18, 2012
  3. Martin FickJan 18, 2012
  4. Martin FickJan 18, 2012
  5. Junio C HamanoJan 18, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.