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

Volume of commits

From
FTFredrik Tolf <fredrik@dolda2000.com>
Date
Jul 12, 2007, 13:16 UTC
Message-ID
<m3ps2xu5hc.fsf@pc7.dolda2000.com>
Hi List,

I was wondering -- whenever I see Git patches committed to projects like the Linux kernel or Git itself, the commits always seems to be committing rather large changes and be rather well-defined in terms of what they change.

When I develop for myself, I usually commit incrementally quite a bit, if for no other reason because Git won't let me switch between branches if I don't commit first. I usually try to keep my commits well-defined, but I don't manage to get anywhere close to what I see when I look at the history of Linux or Git.

So what I'm wondering is how you people manage to do this? Do you actually always commit changes this way (and, in that case, how do you switch between branches)? Or do you somehow aggregate the smaller commits into larger patches and recommit them? Or is there some third possibility that I'm missing?

Fredrik Tolf
Next: VMiklos
Message 1 of 14 in “Volume of commits”
  1. Fredrik TolfJul 12, 2007
  2. VMiklosJul 12, 2007
  3. Johannes SchindelinJul 12, 2007
  4. Sven VerdoolaegeJul 13, 2007
  5. Alex RiesenJul 13, 2007
  6. rebase -i: call editor just once for a multi-squashJohannes Schindelin, Jul 21, 2007
  7. Johannes SchindelinJul 21, 2007
  8. Karl HasselströmJul 12, 2007
  9. Karl HasselströmJul 12, 2007
  10. Fredrik TolfJul 12, 2007
  11. Joshua N PritikinJul 12, 2007
  12. Karl HasselströmJul 12, 2007
  13. Linus TorvaldsJul 12, 2007
  14. Jakub NarebskiJul 13, 2007

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.