git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ben Peart <peartben@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)
Date: Mon, 30 Oct 2017 08:40:36 -0400	[thread overview]
Message-ID: <aa7b33a8-4110-39e4-f722-f87f6b0a8ea5@gmail.com> (raw)
In-Reply-To: <xmqqr2tl40pl.fsf@gitster.mtv.corp.google.com>

> 
> * av/fsmonitor (2017-10-30) 5 commits
>   - SQUASH???
>   - fsmonitor: delay updating state until after split index is merged
>   - fsmonitor: document GIT_TRACE_FSMONITOR
>   - fsmonitor: don't bother pretty-printing JSON from watchman
>   - fsmonitor: set the PWD to the top of the working tree
>   (this branch uses bp/fsmonitor.)
> 
>   Various fixes to bp/fsmonitor topic.
> 
>   What's the status of this one?  I recall that I saw Dscho's "looks
>   good" respose to the cover letter, and Ben sounded positive on most
>   of the patches in the previous series.  Except for the SQUASH??? I
>   had to add to squelch compiler warnings, is this good to go?
> 

This looks good to go from my perspective.

  reply	other threads:[~2017-10-30 12:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  6:19 What's cooking in git.git (Oct 2017, #07; Mon, 30) Junio C Hamano
2017-10-30 12:40 ` Ben Peart [this message]
2017-10-30 17:24 ` Johannes Schindelin
2017-10-30 17:28 ` Johannes Schindelin
2017-10-31  2:38   ` Junio C Hamano
2017-10-31 17:18     ` Johannes Schindelin
2017-10-30 17:31 ` Johannes Schindelin
2017-10-30 19:54   ` Jeff Hostetler
2017-10-31  2:40     ` Junio C Hamano
2017-10-31 13:14       ` Jeff Hostetler
2017-11-01  1:21         ` Junio C Hamano
2017-11-01 17:58           ` Jonathan Tan
2017-11-02  1:13             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aa7b33a8-4110-39e4-f722-f87f6b0a8ea5@gmail.com \
    --to=peartben@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).