From 06f2eaeffd65887ec4181a594d1f2a7a98a1f0cf Mon Sep 17 00:00:00 2001
From: NiveditN <niveditn@gmail.com>
Date: Mon, 9 Oct 2017 12:49:07 +0530
Subject: [PATCH 1/3] doc: added note to fs.watchFile on previousStat

Explains the expected behavior of previousStat in fs.watchFile() when
a watched file disappears and reappears.

Fixes: https://github.com/nodejs/node/issues/15364
---
 doc/api/fs.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/api/fs.md b/doc/api/fs.md
index 0c91ec7b352722..ecab0d5afec379 100644
--- a/doc/api/fs.md
+++ b/doc/api/fs.md
@@ -626,6 +626,19 @@ Any specified file descriptor has to have been opened for appending.
 *Note*: If a file descriptor is specified as the `file`, it will not be closed
 automatically.
 
+*Note:* When a file being watched by `fs.watchFile()` disappears and reappears,
+then the `previousStat` reported in the second callback event (the file's
+reappearance) will be the same as the `previousStat` of the first callback
+event (its disappearance).
+
+This happens when:
+- the file is deleted, followed by a restore
+- the file is renamed twice - the second time back to its original name
+
+In such cases the reappearance callback will not report the `previousStat` of
+the file with all zeroes. This is the correct and expected behavior for
+`uv_fs_poll_start()`, the libuv function that `fs.watchFile()` uses internally.
+
 ## fs.appendFileSync(file, data[, options])
 <!-- YAML
 added: v0.6.7

From 01a8da4e046d080b58d9d4ffb099f13b8bcbe0b1 Mon Sep 17 00:00:00 2001
From: NiveditN <niveditn@gmail.com>
Date: Sat, 14 Oct 2017 12:12:19 +0530
Subject: [PATCH 2/3] doc: corrected position of note on fs.watchFile

Note was previously mistakenly added under fs.appendFile() section.
Now moved to correct position, under fs.watchFile().

The note explains the expected behavior of previousStat in
fs.watchFile() when a watched file disappears and reappears.

Fixes: https://github.com/nodejs/node/issues/15364
---
 doc/api/fs.md | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/doc/api/fs.md b/doc/api/fs.md
index ecab0d5afec379..141784baf664dd 100644
--- a/doc/api/fs.md
+++ b/doc/api/fs.md
@@ -626,19 +626,6 @@ Any specified file descriptor has to have been opened for appending.
 *Note*: If a file descriptor is specified as the `file`, it will not be closed
 automatically.
 
-*Note:* When a file being watched by `fs.watchFile()` disappears and reappears,
-then the `previousStat` reported in the second callback event (the file's
-reappearance) will be the same as the `previousStat` of the first callback
-event (its disappearance).
-
-This happens when:
-- the file is deleted, followed by a restore
-- the file is renamed twice - the second time back to its original name
-
-In such cases the reappearance callback will not report the `previousStat` of
-the file with all zeroes. This is the correct and expected behavior for
-`uv_fs_poll_start()`, the libuv function that `fs.watchFile()` uses internally.
-
 ## fs.appendFileSync(file, data[, options])
 <!-- YAML
 added: v0.6.7
@@ -2575,6 +2562,19 @@ v0.10.
 `fs.unwatchFile`. `fs.watch` should be used instead of `fs.watchFile` and
 `fs.unwatchFile` when possible.
 
+*Note:* When a file being watched by `fs.watchFile()` disappears and reappears,
+then the `previousStat` reported in the second callback event (the file's
+reappearance) will be the same as the `previousStat` of the first callback
+event (its disappearance).
+
+This happens when:
+- the file is deleted, followed by a restore
+- the file is renamed twice - the second time back to its original name
+
+In such cases the reappearance callback will not report the `previousStat` of
+the file with all zeroes. This is the correct and expected behavior for
+`uv_fs_poll_start()`, the libuv function that `fs.watchFile()` uses internally.
+
 ## fs.write(fd, buffer[, offset[, length[, position]]], callback)
 <!-- YAML
 added: v0.0.2

From 1041e87e5eb95e6c9915ac5e46c6596e67c81d89 Mon Sep 17 00:00:00 2001
From: NiveditN <niveditn@gmail.com>
Date: Sat, 14 Oct 2017 15:21:56 +0530
Subject: [PATCH 3/3] doc: updated content of note on fs.watchFile

Removed last paragraph, as per suggestions.

The note explains the expected behavior of previousStat in
fs.watchFile() when a watched file disappears and reappears.

Fixes: https://github.com/nodejs/node/issues/15364
---
 doc/api/fs.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/api/fs.md b/doc/api/fs.md
index 141784baf664dd..58ea4a3bcd1d4f 100644
--- a/doc/api/fs.md
+++ b/doc/api/fs.md
@@ -2571,10 +2571,6 @@ This happens when:
 - the file is deleted, followed by a restore
 - the file is renamed twice - the second time back to its original name
 
-In such cases the reappearance callback will not report the `previousStat` of
-the file with all zeroes. This is the correct and expected behavior for
-`uv_fs_poll_start()`, the libuv function that `fs.watchFile()` uses internally.
-
 ## fs.write(fd, buffer[, offset[, length[, position]]], callback)
 <!-- YAML
 added: v0.0.2