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

Re: [RFC] git-brebase

From
NWNico Williams <nico@cryptonector.com>
Date
Oct 3, 2026, 21:50 UTC
Message-ID
<asF4oOejC7CNqaYu@ubby>
In-Reply-To
<asFy2kOZe7WDy38I@debian>
On Sat, Oct 03, 2026 at 11:29:40PM +0200, Alejandro Colomar wrote:
Show 7 quoted lines
> I'm currently defaulting to brebase for every rebase I want to do.
> 
> However, I still use the regular git-rebase(1) for more precise
> operations.  To be specific, I use it for changing history (without
> moving the base), and I also use it for resolving conflicts as part of
> a git-brebase operation.  They seem to me to be different tools, even
> though they're clearly related.

I see now. Though, of course, if I use git-rebase but don't change the base, then obviously I want a plain rebase. But, ok.

Previous: Alejandro ColomarNext: Alejandro Colomar
Message 8 of 13 in “[RFC] git-brebase”
  1. Alejandro ColomarOct 3, 2026
  2. Alejandro ColomarOct 3, 2026
  3. Nico WilliamsOct 3, 2026
  4. Nico WilliamsOct 3, 2026
  5. Alejandro ColomarOct 3, 2026
  6. Nico WilliamsOct 3, 2026
  7. Alejandro ColomarOct 3, 2026
  8. Nico WilliamsOct 3, 2026
  9. Alejandro ColomarOct 3, 2026
  10. Alejandro ColomarOct 3, 2026
  11. Nico WilliamsOct 3, 2026
  12. Alejandro ColomarOct 3, 2026
  13. Nico WilliamsOct 3, 2026

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.