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

Re: [PATCH] Reintegrate script

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 26, 2009, 11:18 UTC
Message-ID
<alpine.DEB.1.00.0901261218070.14855@racer>
In-Reply-To
<7vd4ea8mnf.fsf@gitster.siamese.dyndns.org>
Hi,
On Mon, 26 Jan 2009, Junio C Hamano wrote:
Show 10 quoted lines
> In a workflow that uses topic branches heavily, you would need to keep 
> updating test integration branch(es) all the time.  If they are managed 
> like my 'next' by merging the tips of topics that have grown since the 
> last integration, it is not so difficult.  You only need to review 
> output from "git branch --no-merged next" to see if there are topics 
> that can and needs to be merged to 'next'.
> 
> But sometimes it is easier to rebuild a test integration branch from
> scratch all the time, especially if you do not publish it for others to
> build on.
FWIW that is exactly what I am aiming at with my rebase -i -p work.

Ciao, Dscho

Previous: Junio C HamanoNext: Bernt Hansen
Message 2 of 3 in “Reintegrate script”
  1. Reintegrate scriptJunio C Hamano, Jan 26, 2009
  2. Johannes SchindelinJan 26, 2009
  3. Meta/Reintegrate: Record all merges to prevent losing topicsBernt Hansen, Feb 13, 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.