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

Re: How to move a big branches to a new base?

From
LMLin Mac <mkl0301@gmail.com>
Date
Mar 3, 2010, 03:17 UTC
Message-ID
<10d816431003021917p54491088ie290ec47840dfaa2@mail.gmail.com>
In-Reply-To
<10d816431002251918vf13a5e8uf0396aa861081bcc@mail.gmail.com>
Hi,

Sorry for re-send this again, for this is really important to me and trouble me a lot. And I've been searching for a long time, but I didn't found any useful.

Or maybe it's the way I uses branch wrong? Should I always keep a branch as clean as possible, and use tag for some unused/not often used branch, to avoid such problem?

Also I doubt whether my last mail reach the mailing list or not. So, any response welcome, even RTFM (I'm actually reading it....) is fine, at least let me know it's just a stupid question.....

Best Regards, Mac Lin

2010/2/26 Lin Mac <mkl0301@gmail.com>:
Show 18 quoted lines
> Hi,
>
> I have a branch that have about 10 descendent branches. Now I would
> like to move this branch, and all the descendent branches, to a new
> base, and I might need to do so quiet frequently before I merge it to
> master branch.
>
> My "dirty" way is to rebase step by step, it takes about 15-20
> rebases, but the branches is somehow complicated, and this seems
> error-prone to me.
>
> Is there a more clean way to do so?
>
> Thanks in advance.
>
> Best Regards,
> Mac Lin
>
Previous: Lin MacNext: John Tapsell
Message 2 of 4 in “How to move a big branches to a new base?”
  1. Lin MacFeb 26, 2010
  2. Lin MacMar 3, 2010
  3. John TapsellMar 3, 2010
  4. Lin MacMar 4, 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.