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
John Tapsell <johnflux@gmail.com>
Date
Mar 3, 2010, 03:54 UTC
Message-ID
<43d8ce651003021954o1411efd2i1a1f26e9b8ed5d54@mail.gmail.com>
In-Reply-To
<10d816431002251918vf13a5e8uf0396aa861081bcc@mail.gmail.com>
On 26 February 2010 03:18, Lin Mac <mkl0301@gmail.com> wrote:
Show 6 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.

I tend to keep my branches as small as possible - a few commits at most. And avoid merges like the plague. This seems to work pretty well. Remember you can squash your commits together to keep the branches clean and well-ordered.

John
Previous: Lin MacNext: Lin Mac
Message 3 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.