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

Re: [PATCH] fsmonitor: option to allow fsmonitor to run against network-mounted repos

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 19, 2022, 10:05 UTC
Message-ID
<4q6248n0-nqr5-p5pp-64s3-qq7nr53q01op@tzk.qr>
In-Reply-To
<pull.1326.git.1660855703816.gitgitgadget@gmail.com>
Hi Eric,
On Thu, 18 Aug 2022, Eric DeCosta via GitGitGadget wrote:
Show 9 quoted lines
> From: Eric DeCosta <edecosta@mathworks.com>
>
> Though perhaps not common, there are uses cases where users have large,
> network-mounted repos. Having the ability to run fsmonitor against
> network paths would benefit those users.
>
> As a first step towards enabling fsmonitor to work against
> network-mounted repos, a configuration option, 'fsmonitor.allowRemote'
> was introduced for Windows.

If you start the commit message along the following lines, it might be easier/quicker to grok the context for the keen reader:

	In 85dc0da6dcf (fsmonitor: option to allow fsmonitor to run against
	network-mounted repos, 2022-08-11), the Windows backend of the
	FSMonitor learned to allow running on network drives, via the
	`fsmonitor.allowRemote` config setting.
Show 8 quoted lines
> Setting this option to true will override the default behavior
> (erroring-out) when a network-mounted repo is detected by fsmonitor. In
> order for macOS to have parity with Windows, the same option is now
> introduced for macOS.
>
> The the added wrinkle being that the Unix domain socket (UDS) file
> used for IPC cannot be created in a network location; instead the
> temporary directory is used.

Thank you very much for this note, after a cursory read I expected that part of the code to be a left-over from some "We know better than the user" type of automatic default, and this paragraph definitely helped me overcome that expectation.

Show 14 quoted lines
>
> Signed-off-by: Eric DeCosta <edecosta@mathworks.com>
> ---
>     fsmonitor: option to allow fsmonitor to run against network-mounted
>     repos
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1326%2Fedecosta-mw%2Ffsmonitor_macos-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1326/edecosta-mw/fsmonitor_macos-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/1326
>
>  compat/fsmonitor/fsm-settings-darwin.c | 77 ++++++++++++++++++++++----
>  fsmonitor-ipc.c                        | 47 +++++++++++++++-
>  fsmonitor-ipc.h                        |  6 ++
>  3 files changed, 117 insertions(+), 13 deletions(-)

I am somewhat puzzled that this has no corresponding change to `Documentation/`.

And now I realize that this was the case also for the patch adding `fsmonitor.allowRemote` support for Windows.

Could I ask you to add a patch to document this config setting?
Show 41 quoted lines
>
> diff --git a/compat/fsmonitor/fsm-settings-darwin.c b/compat/fsmonitor/fsm-settings-darwin.c
> index efc732c0f31..9e2ea3b90cc 100644
> --- a/compat/fsmonitor/fsm-settings-darwin.c
> +++ b/compat/fsmonitor/fsm-settings-darwin.c
> @@ -2,10 +2,28 @@
>  #include "config.h"
>  #include "repository.h"
>  #include "fsmonitor-settings.h"
> +#include "fsmonitor-ipc.h"
>  #include "fsmonitor.h"
>  #include <sys/param.h>
>  #include <sys/mount.h>
>
> +/*
> + * Check if monitoring remote working directories is allowed.
> + *
> + * By default, monitoring remote working directories is
> + * disabled.  Users may override this behavior in enviroments where
> + * they have proper support.
> + */
> +static int check_config_allowremote(struct repository *r)
> +{
> +	int allow;
> +
> +	if (!repo_config_get_bool(r, "fsmonitor.allowremote", &allow))
> +		return allow;
> +
> +	return -1; /* fsmonitor.allowremote not set */
> +}
> +
>  /*
>   * [1] Remote working directories are problematic for FSMonitor.
>   *
> @@ -27,24 +45,22 @@
>   * In theory, the above issues need to be addressed whether we are
>   * using the Hook or IPC API.
>   *
> + * So (for now at least), mark remote working directories as
> + * incompatible by default.
> + *
This was moved up, okay.
Show 11 quoted lines
>   * For the builtin FSMonitor, we create the Unix domain socket for the
> - * IPC in the .git directory.  If the working directory is remote,
> - * then the socket will be created on the remote file system.  This
> - * can fail if the remote file system does not support UDS file types
> - * (e.g. smbfs to a Windows server) or if the remote kernel does not
> - * allow a non-local process to bind() the socket.  (These problems
> - * could be fixed by moving the UDS out of the .git directory and to a
> - * well-known local directory on the client machine, but care should
> - * be taken to ensure that $HOME is actually local and not a managed
> - * file share.)
> + * IPC in the temporary directory.  If the temporary directory is

This is incorrect. It is still the `.git` directory in the common case, not a temporary directory.

Show 11 quoted lines
> + * remote, then the socket will be created on the remote file system.
> + * This can fail if the remote file system does not support UDS file
> + * types (e.g. smbfs to a Windows server) or if the remote kernel does
> + * not allow a non-local process to bind() the socket.
>   *
> - * So (for now at least), mark remote working directories as
> - * incompatible.
> + * Therefore remote UDS locations are marked as incompatible.
>   *
>   *
>   * [2] FAT32 and NTFS working directories are problematic too.
Doesn't this patch address this, too? See below for more on that.
Show 22 quoted lines
>   *
> - * The builtin FSMonitor uses a Unix domain socket in the .git
> + * The builtin FSMonitor uses a Unix domain socket in the temporary
>   * directory for IPC.  These Windows drive formats do not support
>   * Unix domain sockets, so mark them as incompatible for the daemon.
>   *
> @@ -65,6 +81,39 @@ static enum fsmonitor_reason check_volume(struct repository *r)
>  			 "statfs('%s') [type 0x%08x][flags 0x%08x] '%s'",
>  			 r->worktree, fs.f_type, fs.f_flags, fs.f_fstypename);
>
> +	if (!(fs.f_flags & MNT_LOCAL)) {
> +		switch (check_config_allowremote(r)) {
> +		case 0: /* config overrides and disables */
> +			return FSMONITOR_REASON_REMOTE;
> +		case 1: /* config overrides and enables */
> +			return FSMONITOR_REASON_OK;
> +		default:
> +			break; /* config has no opinion */
> +		}
> +
> +		return FSMONITOR_REASON_REMOTE;
> +	}
This `switch()` statement sounds like a verbose way to say the same as:
		return check_config_allowremote(r) == 1 ?
			FSMONITOR_REASON_OK : FSMONITOR_REASON_REMOTE;
Show 5 quoted lines
> +
> +	return FSMONITOR_REASON_OK;
> +}
> +
> +static enum fsmonitor_reason check_uds_volume(void)
What's an UDS volume? Do you mean to say "Unix Domain Socket Volume"?

If so, it would be better to turn this into a function called `filesystem_supports_unix_sockets()` and to return an `int`, 1 for "yes", 0 for "no".

Show 20 quoted lines
> +{
> +	struct statfs fs;
> +	const char *path = fsmonitor_ipc__get_path();
> +
> +	if (statfs(path, &fs) == -1) {
> +		int saved_errno = errno;
> +		trace_printf_key(&trace_fsmonitor, "statfs('%s') failed: %s",
> +				 path, strerror(saved_errno));
> +		errno = saved_errno;
> +		return FSMONITOR_REASON_ERROR;
> +	}
> +
> +	trace_printf_key(&trace_fsmonitor,
> +			 "statfs('%s') [type 0x%08x][flags 0x%08x] '%s'",
> +			 path, fs.f_type, fs.f_flags, fs.f_fstypename);
> +
>  	if (!(fs.f_flags & MNT_LOCAL))
>  		return FSMONITOR_REASON_REMOTE;
>
> @@ -85,5 +134,9 @@ enum fsmonitor_reason fsm_os__incompatible(struct repository *r)

It is unfortunate that the diff hunk stops here, and mails lack a button to increase the diff context. In this instance, the hidden part of the `check_volume()` function is quite interesting: it returns `FSMONITOR_REASON_NOSOCKETS` for `msdos` and `ntfs` file systems.

Which means that your patch changes behavior not only for remote file systems, but also for local ones without support for Unix sockets.

To heed the principle of separation of concerns, please do split out that part. I would recommend to make it the first patch to support `msdos`/`ntfs` file systems (by registering the Unix sockets in a temporary directory instead of the `.git/` directory). The second patch can then introduce support for `fsmonitor.allowRemote` on macOS on top of the first patch.

Show 27 quoted lines
>  	if (reason != FSMONITOR_REASON_OK)
>  		return reason;
>
> +	reason = check_uds_volume();
> +	if (reason != FSMONITOR_REASON_OK)
> +		return reason;
> +
>  	return FSMONITOR_REASON_OK;
>  }
> diff --git a/fsmonitor-ipc.c b/fsmonitor-ipc.c
> index 789e7397baa..6e9b40a03d5 100644
> --- a/fsmonitor-ipc.c
> +++ b/fsmonitor-ipc.c
> @@ -4,6 +4,7 @@
>  #include "fsmonitor-ipc.h"
>  #include "run-command.h"
>  #include "strbuf.h"
> +#include "tempfile.h"
>  #include "trace2.h"
>
>  #ifndef HAVE_FSMONITOR_DAEMON_BACKEND
> @@ -47,7 +48,51 @@ int fsmonitor_ipc__is_supported(void)
>  	return 1;
>  }
>
> -GIT_PATH_FUNC(fsmonitor_ipc__get_path, "fsmonitor--daemon.ipc")
> +GIT_PATH_FUNC(fsmonitor_ipc__get_pathfile, "fsmonitor--daemon.ipc")

Why rename this? That's unnecessary chatter in the patch. Let's avoid such things in the future, it only costs reviewers time.

Show 44 quoted lines
> +
> +static char *gen_ipc_file(void)
> +{
> +	char *retval = NULL;
> +	struct tempfile *ipc;
> +
> +	const char *ipc_file = fsmonitor_ipc__get_pathfile();
> +	FILE *fp = fopen(ipc_file, "w");
> +
> +	if (!fp)
> +		die_errno("error opening '%s'", ipc_file);
> +	ipc = mks_tempfile_t("fsmonitor_ipc_XXXXXX");
> +	strbuf_write(&ipc->filename, fp);
> +	fclose(fp);
> +	retval = strbuf_detach(&ipc->filename, NULL);
> +	strbuf_release(&ipc->filename);
> +	return retval;
> +}
> +
> +const char *fsmonitor_ipc__get_path(void)
> +{
> +	char *retval = NULL;
> +	struct strbuf sb = STRBUF_INIT;
> +
> +	const char *ipc_file = fsmonitor_ipc__get_pathfile();
> +	FILE *fp = fopen(ipc_file, "r");
> +
> +	if (!fp) {
> +		return gen_ipc_file();
> +	} else {
> +		strbuf_read(&sb, fileno(fp), 0);
> +		fclose(fp);
> +		fp = fopen(sb.buf, "r");
> +		if (!fp) { /* generate new file */
> +			if (unlink(ipc_file) < 0)
> +				die_errno("could not remove '%s'", ipc_file);
> +			return gen_ipc_file();
> +		}
> +		fclose(fp);
> +		retval = strbuf_detach(&sb, NULL);
> +		strbuf_release(&sb);
> +		return retval;
> +	}
> +}

I am afraid I do not understand how this code can guarantee a fixed path for the Unix domain socket.

It _needs_ to be fixed so that a singleton daemon can run and listen on it, and an arbitrary number of Git clients can connect to it.

If it is not fixed, you will cause Git to quite possibly start a new FSMonitor daemon for every invocation that wants to connect to an FSMonitor daemon.

This means that the path of the Unix socket needs to have a 1:1 relationship to the path of the `.git/` directory. If you install it in that directory, that invariant is naturally fulfilled. If you want to install it elsewhere, you will have to come up with a reliable way to guarantee that connection.

One option would be to install the Unix sockets in the home directory, under a name like `.git-fsmonitor-<hash>` where the <hash> is e.g. a SHA-1/SHA-256 of the canonicalized path of the `.git/` directory.

Show 20 quoted lines
>
>  enum ipc_active_state fsmonitor_ipc__get_state(void)
>  {
> diff --git a/fsmonitor-ipc.h b/fsmonitor-ipc.h
> index b6a7067c3af..63277dea39e 100644
> --- a/fsmonitor-ipc.h
> +++ b/fsmonitor-ipc.h
> @@ -18,6 +18,12 @@ int fsmonitor_ipc__is_supported(void);
>   */
>  const char *fsmonitor_ipc__get_path(void);
>
> +/*
> + * Returns the pathname to the file that contains the pathname to the
> + * IPC named pipe or Unix domain socket.
> + */
> +const char *fsmonitor_ipc__get_pathfile(void);
> +
>  /*
>   * Try to determine whether there is a `git-fsmonitor--daemon` process
>   * listening on the IPC pipe/socket.

Thank you for working on this, also on the Windows side. It definitely helps!

Ciao, Dscho

Previous: Junio C HamanoNext: Jeff Hostetler
Message 4 of 170 in “fsmonitor: option to allow fsmonitor to run against network-mounted repos”
  1. fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 18, 2022
  2. Junio C HamanoAug 18, 2022
  3. Junio C HamanoAug 18, 2022
  4. Johannes SchindelinAug 19, 2022
  5. Jeff HostetlerAug 19, 2022
  6. Eric DeCostaAug 19, 2022
  7. Jeff HostetlerAug 19, 2022
  8. Eric SunshineAug 19, 2022
  9. Torsten BögershausenAug 19, 2022
  10. Junio C HamanoAug 20, 2022
  11. Johannes SchindelinAug 22, 2022
  12. Junio C HamanoAug 22, 2022
  13. Jeff HostetlerAug 23, 2022
  14. Eric DeCostaAug 24, 2022
  15. 0/4 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 23, 2022
  16. 1/4 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 23, 2022
  17. 2/4 fsmonitor: macOS: allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 23, 2022
  18. 3/4 Check working directory and Unix domain socket file for compatabilityedecosta via GitGitGadget, Aug 23, 2022
  19. 4/4 Minor refactoring and simplification of Windows settings checksedecosta via GitGitGadget, Aug 23, 2022
  20. 0/2 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 23, 2022
  21. 2/2 Check working directory and Unix domain socket file for compatabilityedecosta via GitGitGadget, Aug 23, 2022
  22. Junio C Hamano, Aug 24, 2022
  23. 1/2 fsmonitor: macOS: allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 23, 2022
  24. Junio C HamanoAug 24, 2022
  25. 0/4 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Aug 31, 2022
  26. 1/4 fsmonitor: add two new config options, allowRemote and socketDirEric DeCosta via GitGitGadget, Aug 31, 2022
  27. Ævar Arnfjörð BjarmasonAug 31, 2022
  28. Junio C HamanoAug 31, 2022
  29. Ramsay JonesSep 1, 2022
  30. Jeff HostetlerSep 1, 2022
  31. Jeff HostetlerSep 1, 2022
  32. Jeff HostetlerSep 1, 2022
  33. Eric DeCostaSep 2, 2022
  34. Jeff HostetlerSep 6, 2022
  35. 2/4 fsmonitor: generate unique Unix socket file name in the desired locationEric DeCosta via GitGitGadget, Aug 31, 2022
  36. Ævar Arnfjörð BjarmasonAug 31, 2022
  37. Junio C HamanoAug 31, 2022
  38. 3/4 fsmonitor: ensure filesystem and unix socket filesystem are compatibleEric DeCosta via GitGitGadget, Aug 31, 2022
  39. 4/4 fsmonitor: normalize FSEvents event paths to the real pathEric DeCosta via GitGitGadget, Aug 31, 2022
  40. Ævar Arnfjörð BjarmasonAug 31, 2022
  41. Jeff HostetlerSep 1, 2022
  42. Eric DeCostaSep 2, 2022
  43. Jeff HostetlerSep 6, 2022
  44. Eric DeCostaSep 6, 2022
  45. Eric DeCostaSep 6, 2022
  46. Eric DeCostaSep 6, 2022
  47. Jeff HostetlerSep 7, 2022
  48. Eric DeCostaSep 7, 2022
  49. 0/4 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 10, 2022
  50. 1/4 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 10, 2022
  51. 2/4 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 10, 2022
  52. 3/4 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 10, 2022
  53. 4/4 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 10, 2022
  54. Eric SunshineSep 11, 2022
  55. Junio C HamanoSep 12, 2022
  56. Junio C HamanoSep 12, 2022
  57. Eric DeCostaSep 12, 2022
  58. Junio C HamanoSep 12, 2022
  59. Eric DeCostaSep 12, 2022
  60. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 13, 2022
  61. 1/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 13, 2022
  62. 3/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 13, 2022
  63. Junio C HamanoSep 14, 2022
  64. Eric DeCostaSep 14, 2022
  65. 2/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 13, 2022
  66. 4/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 13, 2022
  67. Junio C HamanoSep 14, 2022
  68. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 13, 2022
  69. 5/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 13, 2022
  70. Jeff HostetlerSep 16, 2022
  71. Eric DeCostaSep 16, 2022
  72. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 16, 2022
  73. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 16, 2022
  74. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 16, 2022
  75. Junio C HamanoSep 16, 2022
  76. Jeff HostetlerSep 19, 2022
  77. Junio C HamanoSep 19, 2022
  78. Jeff HostetlerSep 19, 2022
  79. Junio C HamanoSep 19, 2022
  80. Eric DeCostaSep 19, 2022
  81. Jeff HostetlerSep 20, 2022
  82. Eric DeCostaSep 20, 2022
  83. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 16, 2022
  84. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 16, 2022
  85. 5/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 16, 2022
  86. Junio C HamanoSep 16, 2022
  87. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 16, 2022
  88. Junio C HamanoSep 16, 2022
  89. 0/5 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 17, 2022
  90. 2/5 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 17, 2022
  91. Eric SunshineSep 17, 2022
  92. Junio C HamanoSep 19, 2022
  93. Eric SunshineSep 17, 2022
  94. Eric DeCostaSep 17, 2022
  95. Junio C HamanoSep 19, 2022
  96. 1/5 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 17, 2022
  97. 3/5 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 17, 2022
  98. 4/5 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 17, 2022
  99. 5/5 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 17, 2022
  100. Eric SunshineSep 17, 2022
  101. Eric DeCostaSep 19, 2022
  102. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 19, 2022
  103. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 19, 2022
  104. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 19, 2022
  105. Eric SunshineSep 19, 2022
  106. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 19, 2022
  107. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 19, 2022
  108. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 19, 2022
  109. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 19, 2022
  110. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 20, 2022
  111. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 20, 2022
  112. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 20, 2022
  113. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 20, 2022
  114. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 20, 2022
  115. Jeff HostetlerSep 21, 2022
  116. Eric DeCostaSep 21, 2022
  117. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 20, 2022
  118. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 20, 2022
  119. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 21, 2022
  120. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 21, 2022
  121. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 21, 2022
  122. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 21, 2022
  123. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 21, 2022
  124. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 21, 2022
  125. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 21, 2022
  126. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 24, 2022
  127. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 24, 2022
  128. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 24, 2022
  129. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 24, 2022
  130. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 24, 2022
  131. Ævar Arnfjörð BjarmasonSep 26, 2022
  132. Eric DeCostaSep 27, 2022
  133. Ævar Arnfjörð BjarmasonSep 26, 2022
  134. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 24, 2022
  135. Eric DeCostaSep 25, 2022
  136. Ævar Arnfjörð BjarmasonSep 26, 2022
  137. Eric DeCostaSep 27, 2022
  138. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 24, 2022
  139. Ævar Arnfjörð BjarmasonSep 26, 2022
  140. Eric SunshineSep 27, 2022
  141. Eric DeCostaSep 27, 2022
  142. Eric DeCostaSep 25, 2022
  143. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 27, 2022
  144. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 27, 2022
  145. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 27, 2022
  146. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 27, 2022
  147. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 27, 2022
  148. Ævar Arnfjörð BjarmasonSep 28, 2022
  149. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 27, 2022
  150. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 27, 2022
  151. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Sep 28, 2022
  152. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Sep 28, 2022
  153. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Sep 28, 2022
  154. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Sep 28, 2022
  155. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Sep 28, 2022
  156. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Sep 28, 2022
  157. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Sep 28, 2022
  158. 0/6 fsmonitor: option to allow fsmonitor to run against network-mounted reposEric DeCosta via GitGitGadget, Oct 4, 2022
  159. 1/6 fsmonitor: refactor filesystem checks to common interfaceEric DeCosta via GitGitGadget, Oct 4, 2022
  160. Ævar Arnfjörð BjarmasonJan 30, 2023
  161. 2/6 fsmonitor: relocate socket file if .git directory is remoteEric DeCosta via GitGitGadget, Oct 4, 2022
  162. Ævar Arnfjörð BjarmasonJan 30, 2023
  163. 3/6 fsmonitor: avoid socket location check if using hookEric DeCosta via GitGitGadget, Oct 4, 2022
  164. 5/6 fsmonitor: check for compatability before communicating with fsmonitorEric DeCosta via GitGitGadget, Oct 4, 2022
  165. 4/6 fsmonitor: deal with synthetic firmlinks on macOSEric DeCosta via GitGitGadget, Oct 4, 2022
  166. Ævar Arnfjörð BjarmasonJan 30, 2023
  167. 6/6 fsmonitor: add documentation for allowRemote and socketDir optionsEric DeCosta via GitGitGadget, Oct 4, 2022
  168. Ævar Arnfjörð BjarmasonJan 30, 2023
  169. Junio C HamanoOct 5, 2022
  170. Eric DeCostaOct 5, 2022

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.