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

Re: Branching workflow

From
Javier Domingo Cansino <javierdo1@gmail.com>
Date
Sep 22, 2014, 15:59 UTC
Message-ID
<CALZVapmm3=zgx4xZegieSxiUOcYcz9DMHVFknA8SeeYwO5fVJQ@mail.gmail.com>
In-Reply-To
<CALZVapkvVNxb-jJssZqjT-Y8sApK8O1pe3xTB8guNtx9Md2W6Q@mail.gmail.com>
Hello!,

I have been using this workflow you suggested, and I happen to find it really good fitting in many projects I am.

I would like to seek for a little more advice. I keep rebasing all my work each time master branch is updated, and I would like to know if this is usually done or not.

The workflow is not using emails, but each developer has his clone where he works, and occasionally sends work to the gerrit tool we use, upgrading the patch with each master update.

I know this is a crazy workflow, and I would like to know when you usually consider to update the sent patch with a rebase.

Cheers,
-- 
Javier Domingo Cansino
Previous: Javier DomingoNext: Junio C Hamano
Message 6 of 7 in “Branching workflow”
  1. Javier DomingoDec 3, 2013
  2. John KeepingDec 3, 2013
  3. Javier DomingoDec 3, 2013
  4. Junio C HamanoDec 3, 2013
  5. Javier DomingoDec 3, 2013
  6. Javier Domingo CansinoSep 22, 2014
  7. Junio C HamanoSep 25, 2014

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.