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

Re: Git rebase using "wrong" commit

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 20, 2009, 21:20 UTC
Message-ID
<7vws2plq38.fsf@alter.siamese.dyndns.org>
In-Reply-To
<200910201521.05526.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
Show 9 quoted lines
> Note that there is no real reason to rebase continually unless you
> want to kick out flawed topics or old versions of branches.  For
> example, git.git only rebases 'next' immediately after a release.
> Furthermore, even if you go for the 'pu' model which is rebuilt all
> the time, you can automate this with a script.  There is one in the
> 'todo' branch of git.git, called PU.
>
> (I myself just use a list of topics I want merged, and a simple 'git
> merge $topic' loop.)

I do not use PU nor RB from todo these days, by the way. I instead rebuild my branches with Reintegrate (also from todo).

Previous: Thomas Rast
Message 3 of 3 in “Git rebase using "wrong" commit”
  1. Philip AllisonOct 20, 2009
  2. Thomas RastOct 20, 2009
  3. Junio C HamanoOct 20, 2009

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.