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

Re: [PATCH v3] 0/4 fsmonitor fixes

From
Ben Peart <peartben@gmail.com>
Date
Oct 30, 2017, 12:38 UTC
Message-ID
<7fc39ba0-d1a3-7e96-8585-e82c54dc3e7c@gmail.com>
In-Reply-To
<20171027232637.30395-1-alexmv@dropbox.com>
On 10/27/2017 7:26 PM, Alex Vandiver wrote:
Show 12 quoted lines
> Updates since v2:
> 
>   - Fix tab which crept into 1/4
> 
>   - Fixed the benchmarking code in the commit message in 2/4 to just
>     always load JSON::XS -- the previous version was the version where
>     I'd broken that to force loading of JSON::PP.
> 
>   - Remove the --no-pretty from the t/ version of query-watchman in
>     2/4; I don't know how I messed up diff'ing the file previously, but
>     if there are already differences, it makes sense to let them slide.
> 
Thanks Alex, nice improvements.  This looks good to go.
Previous: Johannes Schindelin
Message 10 of 10 in “0/4 fsmonitor fixes”
  1. 0/4 fsmonitor fixesAlex Vandiver, Oct 27, 2017
  2. 1/4 fsmonitor: Set the PWD to the top of the working treeAlex Vandiver, Oct 27, 2017
  3. 2/4 fsmonitor: Don't bother pretty-printing JSON from watchmanAlex Vandiver, Oct 27, 2017
  4. 3/4 fsmonitor: Document GIT_TRACE_FSMONITORAlex Vandiver, Oct 27, 2017
  5. 4/4 fsmonitor: Delay updating state until after split index is mergedAlex Vandiver, Oct 27, 2017
  6. Junio C HamanoOct 31, 2017
  7. Johannes SchindelinOct 31, 2017
  8. Alex VandiverOct 31, 2017
  9. Johannes SchindelinOct 29, 2017
  10. Ben PeartOct 30, 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.