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

Re: Rebasing Multiple branches at once...

From
RMRick Moynihan <rick@calicojack.co.uk>
Date
Oct 16, 2008, 14:48 UTC
Message-ID
<48F7542B.1050909@calicojack.co.uk>
In-Reply-To
<20081016135908.GI536@genesis.frugalware.org>
Miklos Vajna wrote:
Show 9 quoted lines
> On Thu, Oct 16, 2008 at 01:17:20PM +0100, Rick Moynihan <rick@calicojack.co.uk> wrote:
>> I have a master branch, a dev branch and a number of feature branches from 
>> dev.  And I was wondering if there was an easy way to rebase dev and all of 
>> it's sub-branches onto master.
> 
> In general this is considered harmful. Why do you rebase your branch
> from time to time? For example in git.git, topic branches are based on
> master, then merged to master when they are ready, but they are never
> rebased.

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.

R.
Previous: Miklos VajnaNext: Miklos Vajna
Message 3 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.