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

Re: What's cooking in git.git (Nov 2013, #05; Thu, 21)

From
Thomas Rast <tr@thomasrast.ch>
Date
Nov 22, 2013, 23:04 UTC
Message-ID
<87vbzkghs9.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<20131122223654.GB7538@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> Re-rolling such a big chunk of code _is_ a pain for both me and for
> reviewers, so I wouldn't mind switching to "fixes on top" instead of
> re-rolling at some point. But we can do another round or two of re-roll
> first.

No, actually I think the plan that you sketched in the other side thread sounded nice: give it some exposure in next. I'll still try and read the rest, but that way it hopefully gets (much) more testing.

-- 
Thomas Rast
tr@thomasrast.ch
Previous: Jeff KingNext: Vicent Marti
Message 7 of 15 in “What's cooking in git.git (Nov 2013, #05; Thu, 21)”
  1. Junio C HamanoNov 22, 2013
  2. Jeff KingNov 22, 2013
  3. Thomas RastNov 22, 2013
  4. Jeff KingNov 22, 2013
  5. Thomas RastNov 22, 2013
  6. Jeff KingNov 22, 2013
  7. Thomas RastNov 22, 2013
  8. Vicent MartiNov 22, 2013
  9. Thomas RastNov 22, 2013
  10. Junio C HamanoNov 22, 2013
  11. Vicent MartíNov 22, 2013
  12. Junio C HamanoNov 22, 2013
  13. Jeff KingNov 22, 2013
  14. Antoine PelisseNov 23, 2013
  15. Junio C HamanoNov 25, 2013

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.