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

Re: [PATCH] test-lib: avoid full path to store test results

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 31, 2012, 02:13 UTC
Message-ID
<20121031021318.GB15167@elie.Belkin>
In-Reply-To
<CAMP44s1xAeW2QZsNwRVRx+DEhYVVdiKbw-y-aNuo6unuv7pYZQ@mail.gmail.com>
Felipe Contreras wrote:
> It's all fun and games to write explanations for things, but it's not
> that easy when you want those explanations to be actually true, and
> corrent--you have to spend time to make sure of that.

That's why it's useful for the patch submitter to write them, asking for help when necessary.

As a bonus, it helps reviewers understand the effect of the patch. Bugs averted!

[...]
> Either way, if obvious fixes that are one-liners require an essay for
> you, I give up.

I guess it is fair to call a reasonable subject line plus a couple of sentences an essay. Yes, obvious fixes especially require that, since the bug caused by an obvious fix is one of the worst kinds.

Previous: Felipe ContrerasNext: Felipe Contreras
Message 8 of 18 in “test-lib: avoid full path to store test results”
  1. test-lib: avoid full path to store test resultsFelipe Contreras, Oct 30, 2012
  2. Jeff KingOct 30, 2012
  3. Felipe ContrerasOct 30, 2012
  4. Jonathan NiederOct 30, 2012
  5. Felipe ContrerasOct 30, 2012
  6. Jonathan NiederOct 31, 2012
  7. Felipe ContrerasOct 31, 2012
  8. Jonathan NiederOct 31, 2012
  9. Felipe ContrerasOct 31, 2012
  10. Johannes SixtOct 31, 2012
  11. Felipe ContrerasOct 31, 2012
  12. Jeff KingNov 2, 2012
  13. Felipe ContrerasNov 2, 2012
  14. Jeff KingNov 2, 2012
  15. Elia PintoOct 30, 2012
  16. Jonathan NiederOct 30, 2012
  17. Elia PintoOct 30, 2012
  18. Stefano LattariniOct 31, 2012

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.