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

rebase destroys branches

From
G[Gene Thomas [DATACOM] <gene.thomas@datacom.co.nz>
Date
Mar 4, 2013, 23:06 UTC
Message-ID
<C057AC9B02D06A49810E9597C11F55BF14DFE51C9F@dnzwgex2.datacom.co.nz>
Hello,
          I am evaluating git for use in a company. Please correct if I am wrong. I am concerned that an inexperienced developer could mistakenly rebase branches, destroying the original branch. Attached is a script (Windoze) that shows the 'topic' branch being moved!, after the rebase we are unable to see the original branch, read it's history or find it's commit points.
Surely no operation should remove anything from the repository. Operations like this irreversibly break the repository . When rebasing the original branch must be retained.
Yours faithfully,
Gene Thomas.
Next: Philip Oakley
Message 1 of 5 in “rebase destroys branches”
  1. Gene Thomas [DATACOM]Mar 4, 2013
  2. Philip OakleyMar 4, 2013
  3. Gene Thomas [DATACOM]Mar 5, 2013
  4. Theodore Ts'oMar 5, 2013
  5. Philip OakleyMar 5, 2013

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.