{"thread":{"id":"47621","subject":"[PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself","startedAt":"2018-01-17T05:14:10Z","lastAt":"2018-01-17T18:27:32Z","messageCount":3,"participants":["Yasushi SHOJI","Ben Peart","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"336690","messageId":"20180117050857.10480-1-yashi@atmark-techno.com","threadId":"47621","inReplyTo":null,"subject":"[PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself","fromName":"Yasushi SHOJI","fromEmail":"yashi@atmark-techno.com","sentAt":"2018-01-17T05:08:57Z","receivedAt":"2018-01-17T05:14:10Z","isPatch":true,"sender":{"key":"yashi@atmark-techno.com","avatar":"https://gravatar.com/avatar/4817e8703ac4379935834d87453faa9d0c94b9dc19d83fcc54c67875eb133e59?d=mp&s=160"},"body":"Add a pointer to git-update-index(1) and a bit more detail about\nfsmonitor and watchman to help people following up the new feature.\n---\n\nHi Ben and Junio,\n\nWouldn't it be nice to tell the world a bit more about \"file system\nmonitor\" we now support? I think that \"git status\" and \"watchman\"\nmight not ring the bell for some, but adding a word \"file system\nmonitor\" may.\n\nI know most of repos don't need fsmonitor but it's a cool feature to\nhave it. ;-)\n\nWDYT?\n\n\n Documentation/RelNotes/2.16.0.txt | 7 +++++--\n 1 file changed, 5 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/RelNotes/2.16.0.txt b/Documentation/RelNotes/2.16.0.txt\nindex 919f3eb3e..0c81c5915 100644\n--- a/Documentation/RelNotes/2.16.0.txt\n+++ b/Documentation/RelNotes/2.16.0.txt\n@@ -62,8 +62,11 @@ UI, Workflows & Features\n * The SubmittingPatches document has been converted to produce an\n HTML version via AsciiDoc/Asciidoctor.\n\n- * We learned to talk to watchman to speed up \"git status\" and other\n- operations that need to see which paths have been modified.\n+ * We learned to optionally talk to a file system monitor via new\n+ fsmonitor extension to speed up \"git status\" and other operations\n+ that need to see which paths have been modified. Currently we only\n+ support \"watchman\". See File System Monitor section of\n+ git-update-index(1) for more detail.\n\n * The \"diff\" family of commands learned to ignore differences in\n carriage return at the end of line.\n--\n2.15.1\n"},{"id":"336700","messageId":"DM5PR2101MB090243C1D9F5DA87565D7DEAF4E90@DM5PR2101MB0902.namprd21.prod.outlook.com","threadId":"47621","inReplyTo":"20180117050857.10480-1-yashi@atmark-techno.com","subject":"RE: [PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself","fromName":"Ben Peart","fromEmail":"ben.peart@microsoft.com","sentAt":"2018-01-17T17:26:37Z","receivedAt":"2018-01-17T17:26:45Z","isPatch":true,"sender":{"key":"benpeart@microsoft.com","avatar":"https://avatars.githubusercontent.com/u/15252029?v=4"},"body":"> -----Original Message-----\n> From: Yasushi SHOJI [mailto:yashi@atmark-techno.com]\n> Sent: Wednesday, January 17, 2018 12:09 AM\n> To: Ben Peart ; gitster@pobox.com\n> Cc: git@vger.kernel.org\n> Subject: [PATCH] RelNotes: fsmonitor: add a pointer to man page and the\n> word itself\n> \n> Add a pointer to git-update-index(1) and a bit more detail about fsmonitor\n> and watchman to help people following up the new feature.\n> ---\n> \n> Hi Ben and Junio,\n> \n> Wouldn't it be nice to tell the world a bit more about \"file system monitor\"\n> we now support? I think that \"git status\" and \"watchman\"\n> might not ring the bell for some, but adding a word \"file system monitor\"\n> may.\n> \n\nThanks 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.\n\n> I know most of repos don't need fsmonitor but it's a cool feature to have it. ;-\n> )\n> \n> WDYT?\n> \n> \n> Documentation/RelNotes/2.16.0.txt | 7 +++++--\n> 1 file changed, 5 insertions(+), 2 deletions(-)\n> \n> diff --git a/Documentation/RelNotes/2.16.0.txt\n> b/Documentation/RelNotes/2.16.0.txt\n> index 919f3eb3e..0c81c5915 100644\n> --- a/Documentation/RelNotes/2.16.0.txt\n> +++ b/Documentation/RelNotes/2.16.0.txt\n> @@ -62,8 +62,11 @@ UI, Workflows & Features\n> * The SubmittingPatches document has been converted to produce an\n> HTML version via AsciiDoc/Asciidoctor.\n> \n> - * We learned to talk to watchman to speed up \"git status\" and other\n> - operations that need to see which paths have been modified.\n> + * We learned to optionally talk to a file system monitor via new\n> + fsmonitor extension to speed up \"git status\" and other operations\n> + that need to see which paths have been modified. Currently we only\n> + support \"watchman\". See File System Monitor section of\n> + git-update-index(1) for more detail.\n> \n> * The \"diff\" family of commands learned to ignore differences in\n> carriage return at the end of line.\n> --\n> 2.15.1\n"},{"id":"336708","messageId":"xmqqo9lss5mb.fsf@gitster.mtv.corp.google.com","threadId":"47621","inReplyTo":"DM5PR2101MB090243C1D9F5DA87565D7DEAF4E90@DM5PR2101MB0902.namprd21.prod.outlook.com","subject":"Re: [PATCH] RelNotes: fsmonitor: add a pointer to man page and the word itself","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-01-17T18:27:24Z","receivedAt":"2018-01-17T18:27:32Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ben Peart writes:\n\n> It's important to note that the support for file system monitors\n> in git is generic - any file system monitor can be integrated with\n> the proper hook/script. We just provided a Perl script to\n> integrate with Watchman as a usable sample as Watchman is already\n> available on several platforms.\n\nMentioning only \"FS monitor\" is insufficient (it would merely\nfrustrate those with FS monitor that is not watchman, after they\nwaste more time to find out that we only do watchman right now).\nMentioning only \"Watchman\" *is* sufficient, though.\n\nMentioning both would be ideal, i.e. e.g. \"We now have a generic\nmechanism to talk to FS monitors to optimize checks of working tree\nfiles, and this version of Git can talk to Watchman using the\nmechanism\". And that is what Yashi's suggestion did, if I am not\nmistaken.\n\n\n"}]}