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

Re: Groups of commits

From
MPMichael Poole <mdpoole@troilus.org>
Date
Apr 28, 2010, 02:15 UTC
Message-ID
<87sk6ge312.fsf@troilus.org>
In-Reply-To
<j2u43d8ce651004271859t8f306261n330004142a42b6df@mail.gmail.com>
John Tapsell writes:
Show 15 quoted lines
> Hi all,
>
>   In my work place, we have a lot of strict rules to get something
> committed.  The code has to pass against a large test suite, it has to
> be tested on different hardware, and so on.
>
>   The problem is that it forces everyone to have one single large
> commit for a week's work.  All the intermediate stages get squashed
> and that history forever lost.
>
>   It would be nice to have a commit in the repository, treated as a
> single commit for all purposes, but then be able to split it into
> multiple commits if necessary.
>
>   Any ideas?

Isn't that what topic branches are for? When development is done on a short-lived branch (hopefully one with a descriptive name), the only commit that needs to go through that process is the merge onto the integration branch.

Michael Poole
Previous: Jeff KingNext: Tay Ray Chuan
Message 3 of 6 in “Groups of commits”
  1. John TapsellApr 28, 2010
  2. Jeff KingApr 28, 2010
  3. Michael PooleApr 28, 2010
  4. Tay Ray ChuanApr 28, 2010
  5. Alex RiesenApr 28, 2010
  6. Avery PennarunApr 28, 2010

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.