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

Re: How to commit incomplete changes?

From
Tomas Carnecky <tom@dbservice.com>
Date
Dec 16, 2011, 01:49 UTC
Message-ID
<4EEAA3C5.2070907@dbservice.com>
In-Reply-To
<4cfc9cf0515b1bc751f6aa0de4f55e2a@ulrik.uio.no>
On 12/15/11 12:24 AM, Hallvard B Furuseth wrote:
> I'm about to commit some small edits which go together with bigger
> generated changes.  It seems both more readable and more cherry-pick-
> friendly to me to keep these in separate commits.

Why do you store generated code? Usually you only store what is absolutely necessary. That means generated code should be generated as needed (part of the build process for example).

tom
Previous: Hallvard Breien Furuseth
Message 10 of 10 in “How to commit incomplete changes?”
  1. Hallvard B FurusethDec 14, 2011
  2. Alexey ShumkinDec 15, 2011
  3. Hallvard B FurusethDec 15, 2011
  4. Alexey ShumkinDec 15, 2011
  5. Alexey ShumkinDec 15, 2011
  6. Neal KreitzingerDec 15, 2011
  7. Junio C HamanoDec 16, 2011
  8. Hallvard Breien FurusethDec 16, 2011
  9. Hallvard Breien FurusethDec 16, 2011
  10. Tomas CarneckyDec 16, 2011

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.