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

Re: What's cooking in git.git (Jan 2017, #04; Mon, 23)

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 25, 2017, 22:51 UTC
Message-ID
<xmqq7f5i92jk.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170125183924.6yclcjl4ggcu42yp@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> I guess the way to dig would be to add a test that looks at the output
> of "type mv" or something, push it to a Travis-hooked branch, and then
> wait for the output
Sounds tempting ;-)
Previous: Jeff KingNext: Lars Schneider
Message 9 of 15 in “What's cooking in git.git (Jan 2017, #04; Mon, 23)”
  1. Junio C HamanoJan 24, 2017
  2. Lars SchneiderJan 24, 2017
  3. Jeff KingJan 24, 2017
  4. Lars SchneiderJan 24, 2017
  5. Johannes SchindelinJan 25, 2017
  6. Jeff KingJan 25, 2017
  7. Junio C HamanoJan 25, 2017
  8. Jeff KingJan 25, 2017
  9. Junio C HamanoJan 25, 2017
  10. Lars SchneiderJan 26, 2017
  11. Lars SchneiderJan 26, 2017
  12. Jeff KingJan 26, 2017
  13. Junio C HamanoJan 26, 2017
  14. Stefan BellerJan 25, 2017
  15. Junio C HamanoJan 25, 2017

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.