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

RE: [EXTERNAL] Re: [PATCH v3] trace2: only include "fsync" events if we git_fsync()

From
Neeraj Singh (WINDOWS-SFS) <neerajsi@microsoft.com>
Date
Jul 18, 2022, 19:01 UTC
Message-ID
<LV2PR21MB3157899077CD86F1949024D1CC8C9@LV2PR21MB3157.namprd21.prod.outlook.com>
In-Reply-To
<xmqq5yjus6u2.fsf@gitster.g>
Yes, ACK.  Looks fine to me.  This is still enough info to diagnose if the configuration is being parsed properly and if we're going down the right codepaths.

Thanks, Neeraj

Previous: Junio C Hamano
Message 8 of 8 in “trace2: don't include "fsync" events in all trace2 logs”
  1. trace2: don't include "fsync" events in all trace2 logsÆvar Arnfjörð Bjarmason, Jun 23, 2022
  2. Neeraj Singh (WINDOWS-SFS)Jun 23, 2022
  3. Junio C HamanoJun 23, 2022
  4. trace2: don't include "fsync" events in all trace2 logsÆvar Arnfjörð Bjarmason, Jun 30, 2022
  5. Junio C HamanoJun 30, 2022
  6. trace2: only include "fsync" events if we git_fsync()Ævar Arnfjörð Bjarmason, Jul 18, 2022
  7. Junio C HamanoJul 18, 2022
  8. Neeraj Singh (WINDOWS-SFS)Jul 18, 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.