git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ben Peart <Ben.Peart@microsoft.com>
To: Yasushi SHOJI <yashi@atmark-techno.com>,
	"gitster@pobox.com" <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: [PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself
Date: Wed, 17 Jan 2018 17:26:37 +0000	[thread overview]
Message-ID: <DM5PR2101MB090243C1D9F5DA87565D7DEAF4E90@DM5PR2101MB0902.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20180117050857.10480-1-yashi@atmark-techno.com>

> -----Original Message-----
> From: Yasushi SHOJI [mailto:yashi@atmark-techno.com]
> Sent: Wednesday, January 17, 2018 12:09 AM
> To: Ben Peart <Ben.Peart@microsoft.com>; gitster@pobox.com
> Cc: git@vger.kernel.org
> Subject: [PATCH] RelNotes: fsmonitor: add a pointer to man page and the
> word itself
> 
> Add a pointer to git-update-index(1) and a bit more detail about fsmonitor
> and watchman to help people following up the new feature.
> ---
> 
> Hi Ben and Junio,
> 
> Wouldn't it be nice to tell the world a bit more about "file system monitor"
> we now support?  I think that "git status" and "watchman"
> might not ring the bell for some, but adding a word "file system monitor"
> may.
> 

Thanks for the call out!  It would be great if everyone who has larger repos and experiencing slower command performance could learn about the new file system monitor support.  I'm not sure if editing the release notes would be enough to do that or not. 😊  It's important to note that the support for file system monitors in git is generic - any file system monitor can be integrated with the proper hook/script.  We just provided a Perl script to integrate with Watchman as a usable sample as Watchman is already available on several platforms.

> I know most of repos don't need fsmonitor but it's a cool feature to have it. ;-
> )
> 
> WDYT?
> 
> 
>  Documentation/RelNotes/2.16.0.txt | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/RelNotes/2.16.0.txt
> b/Documentation/RelNotes/2.16.0.txt
> index 919f3eb3e..0c81c5915 100644
> --- a/Documentation/RelNotes/2.16.0.txt
> +++ b/Documentation/RelNotes/2.16.0.txt
> @@ -62,8 +62,11 @@ UI, Workflows & Features
>   * The SubmittingPatches document has been converted to produce an
>     HTML version via AsciiDoc/Asciidoctor.
> 
> - * We learned to talk to watchman to speed up "git status" and other
> -   operations that need to see which paths have been modified.
> + * We learned to optionally talk to a file system monitor via new
> +   fsmonitor extension to speed up "git status" and other operations
> +   that need to see which paths have been modified.  Currently we only
> +   support "watchman".  See File System Monitor section of
> +   git-update-index(1) for more detail.
> 
>   * The "diff" family of commands learned to ignore differences in
>     carriage return at the end of line.
> --
> 2.15.1

  reply	other threads:[~2018-01-17 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17  5:08 [PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself Yasushi SHOJI
2018-01-17 17:26 ` Ben Peart [this message]
2018-01-17 18:27   ` 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=DM5PR2101MB090243C1D9F5DA87565D7DEAF4E90@DM5PR2101MB0902.namprd21.prod.outlook.com \
    --to=ben.peart@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=yashi@atmark-techno.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).