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

Re: [PATCH v3] git checkout -b: unparent the new branch with -o

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2010, 05:23 UTC
Message-ID
<7v4okfiksh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100317041307.GA26641@progeny.tock>
Jonathan Nieder <jrnieder@gmail.com> writes:
> Junio was discussing the case B.

Well, not really. Even as an ingredient, "nuke index, leaving files in the work tree around" is the most difficult-to-use mode of operation. Either "try to run 'git rm -f .' from the toplevel and only if it succeeds point HEAD to an unborn branch" (aka "remove both"), or "point HEAD to an unborn branch without doing anything else" (aka "keep both") would be an ingredient that is far easier to use.

Previous: Jonathan NiederNext: Jonathan Nieder
Message 5 of 9 in “git checkout -b: unparent the new branch with -o”
  1. git checkout -b: unparent the new branch with -oErick Mattos, Mar 16, 2010
  2. Junio C HamanoMar 16, 2010
  3. Erick MattosMar 17, 2010
  4. Jonathan NiederMar 17, 2010
  5. Junio C HamanoMar 17, 2010
  6. Jonathan NiederMar 17, 2010
  7. Junio C HamanoMar 17, 2010
  8. Erick MattosMar 17, 2010
  9. Junio C HamanoMar 17, 2010

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.