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

Re: Rebasing Multiple branches at once...

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Oct 16, 2008, 21:00 UTC
Message-ID
<20081016210002.GJ536@genesis.frugalware.org>
In-Reply-To
<48F7542B.1050909@calicojack.co.uk>
On Thu, Oct 16, 2008 at 03:48:11PM +0100, Rick Moynihan <rick@calicojack.co.uk> wrote:
Show 5 quoted lines
> Yes, but my understanding is that it's only harmful if you publish the 
> branch (or dependent branches) which are being rebased.
> 
> So rebasing is very bad in these circumstances, but I fail to see why it's 
> bad if these branches are kept private.
Ah, I thought you publish your branches.

One reason may be that if you use merge, no history is lost, if you use rebase, history is in the reflogs, so it'll be lost after some time. But if you know what you are doing, then this is not a problem.

Previous: Rick MoynihanNext: Junio C Hamano
Message 4 of 9 in “Rebasing Multiple branches at once...”
  1. Rick MoynihanOct 16, 2008
  2. Miklos VajnaOct 16, 2008
  3. Rick MoynihanOct 16, 2008
  4. Miklos VajnaOct 16, 2008
  5. Junio C HamanoOct 17, 2008
  6. David KastrupOct 16, 2008
  7. Rick MoynihanOct 16, 2008
  8. Robin BurchellOct 16, 2008
  9. Toby AllsoppOct 16, 2008

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.