Thomas Wolf b6ca1993b0 FS: write to JGit config in a background thread ... Otherwise locking problems may ensue if the JGit config itself is on a different file system. Since the internal is already updated, it is not really important when exactly the value gets persisted. By queueing up separate Runnables executed by a single thread we avoid concurrent write access to the JGit config, and nested calls to getFileStoreAttributes(Path) result in serialized attempts to write. The thread for writing the config must not be a daemon thread. If it were, JVM shutdown might kill it anytime, which may lead to the config not being written, or worse, a config.lock file being left behind. Bug: 566170 Change-Id: I07e3d4c5e029d3cec9ab5895002fc4e0c7948c40 Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>		2020-08-21 09:00:06 +02:00
..
.settings	Decouple JSch from JGit Core	2020-06-01 01:46:59 +02:00
META-INF	Prepare 5.9.0-SNAPSHOT builds	2020-06-09 12:51:12 +02:00
findBugs	[findBugs] Silence warning about Transport initialization	2012-09-14 00:01:47 +02:00
resources/org/eclipse/jgit	DirCache: support index V4	2020-08-15 12:47:45 +02:00
src/org/eclipse/jgit	FS: write to JGit config in a background thread	2020-08-21 09:00:06 +02:00
.classpath	…
.fbprefs	…
.gitignore	…
.project	…
BUILD	Bazel: Add workspace status command to stamp final artifact	2020-07-17 01:10:15 +02:00
about.html	SHA-1: collision detection support	2017-02-28 16:38:43 -08:00
build.properties	…
plugin.properties	Fix bundle localization of Apache SSH bundle	2019-06-21 17:54:06 +02:00
pom.xml	Prepare 5.9.0-SNAPSHOT builds	2020-06-09 12:51:12 +02:00