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

Re: Development strategy

From
LWLea Wiemann <lewiemann@gmail.com>
Date
Jun 2, 2008, 22:36 UTC
Message-ID
<484475FC.8020804@gmail.com>
In-Reply-To
<bd6139dc0806021130p2cc442a3qfe9c00681fdb05e3@mail.gmail.com>
Sverre Rabbelier wrote:
> Keep your commit strategy as is [with small commits],
> and create a branch whenever you want review and in that branch you
> squash the commits as appropriate

Are you suggesting that the squashed patches get merged, or that the squashed patches get reviewed but the finer-granulated patches get merged? In the former case, I'd probably prefer to work with larger patches in the first place (and not just squash them on the review branch), since they are easier to handle -- e.g. I sometimes need to go back and change things in earlier commits, and in those cases larger commits are easier.

-- Lea
Previous: Johannes SchindelinNext: Sverre Rabbelier
Message 8 of 10 in “Development strategy”
  1. Lea WiemannJun 2, 2008
  2. Sverre RabbelierJun 2, 2008
  3. Jakub NarebskiJun 2, 2008
  4. Sverre RabbelierJun 2, 2008
  5. Johannes SchindelinJun 2, 2008
  6. Stephan BeyerJun 2, 2008
  7. Johannes SchindelinJun 2, 2008
  8. Lea WiemannJun 2, 2008
  9. Sverre RabbelierJun 2, 2008
  10. Junio C HamanoJun 2, 2008

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.