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

Commit order in git.git, was Re: [RFC] Two conceptually distinct commit commands

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 6, 2006, 09:54 UTC
Message-ID
<Pine.LNX.4.63.0612061052490.28348@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<874ps91v79.wl%cworth@cworth.org>
Hi,
On Tue, 5 Dec 2006, Carl Worth wrote:
Show 10 quoted lines
> On Tue, 05 Dec 2006 17:13:20 -0800, Junio C Hamano wrote:
> > (This is offtopic)
> 
> It's an interesting topic nonetheless, so I'll comment anyway.
> 
> >  (1) one commit exposes, then another fixes.
> >  (2) one commit fixes, then another verifies the bug is no more.
> >  (3) one commit to include both.
> 
> I feel very strongly that I want (1) in the history.

Note that (1) maybe would reflect history better, but (2) and (3) are way nicer to bisecting.

I fell very strongly that I want (3) in the history.
(Though I am guilty of many instances of (2)...)

Ciao, Dscho

Previous: Carl WorthNext: Carl Worth
Message 10 of 13 in “[RFC] Two conceptually distinct commit commands”
  1. Carl WorthDec 4, 2006
  2. Carl WorthDec 4, 2006
  3. Jakub NarebskiDec 4, 2006
  4. Carl WorthDec 5, 2006
  5. Theodore TsoDec 5, 2006
  6. Junio C HamanoDec 5, 2006
  7. Carl WorthDec 5, 2006
  8. Junio C HamanoDec 6, 2006
  9. Carl WorthDec 6, 2006
  10. Commit order in git.git, was Re: [RFC] Two conceptually distinct commit commandsJohannes Schindelin, Dec 6, 2006
  11. Carl WorthDec 6, 2006
  12. Junio C HamanoDec 6, 2006
  13. Carl WorthDec 6, 2006

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.