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

Re: Rebasing a branch that contains merges

From
A.J. Rossini <blindglobe@gmail.com>
Date
Feb 19, 2007, 14:39 UTC
Message-ID
<1abe3fa90702190639g3e0d6da1xa8086999ca53228@mail.gmail.com>
In-Reply-To
<200702191048.24091.andyparkins@gmail.com>
On 2/19/07, Andy Parkins <andyparkins@gmail.com> wrote:
> So - rebase would need some sort of language to tell it which branch to
> favour.

The more I use git, the more I start thinking that a domain-specific language to describe merges would not be a bad thing. It's so easy (painless, thought-free) to create a complex set of branches that you'd like to rearrange with each other.

Of course, perhaps the right solution is to be simpler and old fashioned and cease hyper-multitasking (i.e. shooting myself in the foot).

(I'm sharing Andy's assumption that my repo is just mine, not really shared -- add in sharing, or public use, and it gets far more complex, and the language idea might be a good idea, and not just an idea. Darcs has it's theory of patches, though it's not a language).

best, -tony

blindglobe@gmail.com Muttenz, Switzerland. "Commit early,commit often, and commit in a repository from which we can easily roll-back your mistakes" (AJR, 4Jan05).

Previous: Andy Parkins
Message 4 of 4 in “Rebasing a branch that contains merges”
  1. Andy ParkinsFeb 19, 2007
  2. Junio C HamanoFeb 19, 2007
  3. Andy ParkinsFeb 19, 2007
  4. A.J. RossiniFeb 19, 2007

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.