Thomas Wolf a29d11775c Atomic file creation: hard-linking may not be allowed ... Android for instance forbids hard linking via a SELinux policy. If we can't hard link, the NFS work-around for atomic file creation cannot work at all. In this case, fall back to not using the hard-linking mechanism. Android throws an AccessDeniedException, so we catch that. The javadoc on Files.createLink() indicates that another possibility might be a SecurityException, so catch that, too. Bug: 543956 Change-Id: I551b7a45f7b2fbbd8cf94f0b7233dbd8a200520e Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>		2019-02-02 23:23:46 +01:00
..
.settings	Move BaseReceivePack#advertisedRefs getter and setter to ReceivePack	2018-12-29 11:59:27 +01:00
META-INF	Implement signing commits using BouncyCastle	2019-01-16 10:05:10 +01:00
findBugs	[findBugs] Silence warning about Transport initialization	2012-09-14 00:01:47 +02:00
resources/org/eclipse/jgit	RenameBranchCommand: more consistent handling of short ref names	2019-01-23 19:10:36 +01:00
src/org/eclipse/jgit	Atomic file creation: hard-linking may not be allowed	2019-02-02 23:23:46 +01:00
.classpath	Change JGit minimum execution environment to JavaSE-1.8	2016-09-20 11:32:36 +02:00
.fbprefs	…
.gitignore	…
.project	Revert "Hide Maven target directories from Eclipse"	2010-08-28 09:50:50 +02:00
BUILD	Bazel: Format BUILD file with buildifier	2019-01-24 11:43:37 +09:00
about.html	SHA-1: collision detection support	2017-02-28 16:38:43 -08:00
build.properties	…
plugin.properties	Remove incubation marker	2011-05-31 22:53:53 +02:00
pom.xml	Implement signing commits using BouncyCastle	2019-01-16 10:05:10 +01:00