1f010d6bdf
We presently use the ".txt" extension for our AsciiDoc files. While not wrong, most editors do not associate this extension with AsciiDoc, meaning that contributors don't get automatic editor functionality that could be useful, such as syntax highlighting and prose linting. It is much more common to use the ".adoc" extension for AsciiDoc files, since this helps editors automatically detect files and also allows various forges to provide rich (HTML-like) rendering. Let's do that here, renaming all of the files and updating the includes where relevant. Adjust the various build scripts and makefiles to use the new extension as well. Note that this should not result in any user-visible changes to the documentation. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
20 lines
973 B
Plaintext
20 lines
973 B
Plaintext
worktree.guessRemote::
|
|
If no branch is specified and neither `-b` nor `-B` nor
|
|
`--detach` is used, then `git worktree add` defaults to
|
|
creating a new branch from HEAD. If `worktree.guessRemote` is
|
|
set to true, `worktree add` tries to find a remote-tracking
|
|
branch whose name uniquely matches the new branch name. If
|
|
such a branch exists, it is checked out and set as "upstream"
|
|
for the new branch. If no such match can be found, it falls
|
|
back to creating a new branch from the current HEAD.
|
|
|
|
worktree.useRelativePaths::
|
|
Link worktrees using relative paths (when "true") or absolute
|
|
paths (when "false"). This is particularly useful for setups
|
|
where the repository and worktrees may be moved between
|
|
different locations or environments. Defaults to "false".
|
|
+
|
|
Note that setting `worktree.useRelativePaths` to "true" implies enabling the
|
|
`extension.relativeWorktrees` config (see linkgit:git-config[1]),
|
|
thus making it incompatible with older versions of Git.
|