summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJacek Centkowski <geminica.programs@gmail.com>2021-11-26 07:12:41 +0000
committerGerrit Code Review <noreply-gerritcodereview@google.com>2021-11-26 07:12:41 +0000
commitd9f7c9387119e67bef20fe795975763f3bf50be9 (patch)
tree1e9444da7869ce5294bd51d2ad6a6b3c639e455b
parent40db47a0b46027903a43ae2d8c724dededa22014 (diff)
parent653caf7f9b1a63f7c7b52db2360e3e1b31faf00e (diff)
Merge "Doc: remoteNameStyle might result in a repo name clashes" into stable-3.2upstream/stable-3.2
-rw-r--r--src/main/resources/Documentation/config.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md
index 9fbede3..13e10ea 100644
--- a/src/main/resources/Documentation/config.md
+++ b/src/main/resources/Documentation/config.md
@@ -450,6 +450,14 @@ remote.NAME.remoteNameStyle
Gerrit server, e.g. `${name}` of `foo/bar/my-repo.git` would
be `my-repo`.
+ > **NOTE**: The use of repository name translation using `remoteNameStyle`
+ > may lead to dangerous situations if there are multiple repositories
+ > that may be mapped to the same target name. For instance when
+ > mapping `/foo/my-repo.git` to `my-repo` using "basenameOnly"
+ > would also map `/bar/my-repo.git` to the same `my-repo` leading
+ > to conflicts where commits can be lost between the two repositories
+ > replicating to the same target `my-repo`.
+
By default, "slash", i.e. remote names will contain slashes as
they do in Gerrit.