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

Rebasing published branches?

From
JWJosef Wolf <jw@raven.inka.de>
Date
Nov 6, 2012, 20:18 UTC
Message-ID
<20121106201822.GE28437@raven.wolf.lan>
Hello,
I know, I should never rebase published branches. But...

I frequently work on different computers and would like to share my private branches across them. When done and the feature is in a good shape, I'd like to rebase to clean up history before I make it available to other people.

I guess rebasing such branches would be OK as long as I can reliably remember to delete those branches on _all_ the clones I ever created.

But waht if I ever make a mistake? How would one recover from such rebase disasters? Anybody knows a good description how such a recover would be done?

Next: Andrew Ardill
Message 1 of 3 in “Rebasing published branches?”
  1. Josef WolfNov 6, 2012
  2. Andrew ArdillNov 6, 2012
  3. Antony MaleNov 6, 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.