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 4, 2010, 09:34 UTC
Message-ID
<10d816431003040134j103c567if10aacf0fa10701f@mail.gmail.com>
In-Reply-To
<43d8ce651003021954o1411efd2i1a1f26e9b8ed5d54@mail.gmail.com>
2010/3/3 John Tapsell <johnflux@gmail.com>:
Show 5 quoted lines
> 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.
squash is a powerful tools, but doens't help much in this situation.

In other word, one have to prevent a branch to becoming a tree. Does it worth to have a new tool for such situation?

Best Regard, Mac Lin

Previous: John Tapsell
Message 4 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.