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

Re: What's cooking in git.git (Feb 2018, #03; Wed, 21)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 27, 2018, 19:13 UTC
Message-ID
<xmqq7eqyqm8n.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<CABPp-BEZ+a4aKvMbQpSeJWh5v_o+BAHhO7Az50Dr4nahH67y=g@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
> patches.  It's a trivial change and squashes cleanly, but if you're
> merging this series to next, I'm curious whether I should submit this
> change as a new patch on top of the series, if you'd prefer a full
> re-roll of the whole series, or something else.

If it is a trivial squash to just a few steps, sending them alone and having me squash them would be the simplest, as that would give a much better visibility to the last minute clean-ups these fixup patches make to the reviewers than a reroll of the whole gargantuan series.

Thanks.
Previous: Elijah NewrenNext: Duy Nguyen
Message 10 of 13 in “What's cooking in git.git (Feb 2018, #03; Wed, 21)”
  1. Junio C HamanoFeb 22, 2018
  2. Brandon WilliamsFeb 22, 2018
  3. Junio C HamanoFeb 22, 2018
  4. Johannes SchindelinFeb 23, 2018
  5. Junio C HamanoFeb 23, 2018
  6. Johannes SchindelinFeb 26, 2018
  7. Junio C HamanoFeb 27, 2018
  8. Phillip WoodFeb 23, 2018
  9. Elijah NewrenFeb 23, 2018
  10. Junio C HamanoFeb 27, 2018
  11. Duy NguyenFeb 26, 2018
  12. Eric SunshineFeb 26, 2018
  13. Jeff HostetlerFeb 27, 2018

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.