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

Re: [PATCH] tests: fix incorrect --write-junit-xml code

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 10, 2022, 18:44 UTC
Message-ID
<xmqqpmh8kkfb.fsf@gitster.g>
In-Reply-To
<3qn5r283-3232-4s58-8q9s-n67o407nr816@tzk.qr>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> The funny thing is that you're usually simply not picking up patches that
> do not get any reviews, but for these refactorings it is somehow
> different, and I do not understand why it needs to be different.

Well, I am not sure if encouraging the maintainer to drop patches that are not reviewed is a good overall direction you would want to go in.

But let's try that. Less work for me, less disruption to our tree, and the world may be quieter and more pleasant ;-)

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 9 in “tests: fix incorrect --write-junit-xml code”
  1. tests: fix incorrect --write-junit-xml codeJohannes Schindelin via GitGitGadget, Jul 14, 2022
  2. Junio C HamanoJul 14, 2022
  3. Ævar Arnfjörð BjarmasonJul 15, 2022
  4. Johannes SchindelinAug 8, 2022
  5. Junio C HamanoAug 8, 2022
  6. Johannes SchindelinAug 9, 2022
  7. Junio C HamanoAug 10, 2022
  8. Johannes SchindelinAug 12, 2022
  9. never refactor v.s. testing (was: [PATCH] tests: fix incorrect --write-junit-xml code)Ævar Arnfjörð Bjarmason, Jul 15, 2022

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.