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

Re: How to commit incomplete changes?

From
HFHallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Date
Dec 16, 2011, 12:58 UTC
Message-ID
<hbf.20111216ym10@bombur.uio.no>
In-Reply-To
<hbf.20111216xubv@bombur.uio.no>
I wrote:
Show 5 quoted lines
>[Neal Kreitzinger]
>> I assume by 'generated changes' you mean the automerge in git...
> 
> No.  And to your questions of why I want this with unpublished work:
> No.  Like I wrote, I'm talking about published commits.

Wait, I see - as-yet unpublished commits, yes. Which seem best to me to publish that way. And which will get cherry-picked later, after commit and testing.

-- 
Hallvard
Previous: Hallvard Breien FurusethNext: Tomas Carnecky
Message 9 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.