Hello,

On Sun, Oct 05, 2025 at 10:52:51PM +0200, Jean-Noël AVILA wrote:

On Thursday, 2 October 2025 17:51:34 CEST Michal Suchanek wrote:

quoted

Also add advice to put new worktrees outside of existing ones.

Signed-off-by: Michal Suchanek <redacted>
---
 Documentation/git-worktree.adoc | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-worktree.adoc b/Documentation/git-

worktree.adoc

quoted

index 389e669ac0..ec31863aec 100644

--- a/Documentation/git-worktree.adoc
+++ b/Documentation/git-worktree.adoc

@@ -79,6 +79,9 @@ with a matching name, treat as equivalent to:
 $ git worktree add --track -b <branch> <path> <remote>/<branch>
 ------------
 +
+For best results it is advised to specify <path> outside of the repository 

and

quoted

+existing worktrees - see <<EXAMPLES>>

Please use the form <<EXAMPLES,EXAMPLES>> in order to let the translators also 
change the cross-link text in their language.

Also, the <path> placeholder should be formatted as _<path>_. For your 
information, I'm right in the middle of pushing the conversion of git-
worktree.adoc to the new synopsis style. 

Seems it would not conflict too badly, at least if your series is
applied first.

Thanks

Michal

quoted

++
 If the branch exists in multiple remotes and one of them is named by
 the `checkout.defaultRemote` configuration variable, we'll use that
 one for the purposes of disambiguation, even if the `<branch>` isn't

@@ -502,8 +505,8 @@ locked "reason\nwhy is locked"
 ...
 ------------

-EXAMPLES
---------
+[[EXAMPLES]]EXAMPLES
+--------------------

As noted by others, please put the block anchors on a dedicated line, out of 
the translation scope.

Thank you.