From: Eric Sunshine <email@example.com> To: firstname.lastname@example.org Cc: "Duy Nguyen" <email@example.com>, "Junio C Hamano" <firstname.lastname@example.org>, "Taylor Blau" <email@example.com>, "Martin Ågren" <firstname.lastname@example.org>, "Eric Sunshine" <email@example.com> Subject: [PATCH v2 5/5] git-wortkree.txt: link to man pages when citing other Git commands Date: Mon, 3 Aug 2020 20:55:35 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> When citing other Git commands, rather than merely formatting them with a fixed-width typeface, improve the reader experience by linking to them directly via `linkgit:`. Suggested-by: Martin Ågren <firstname.lastname@example.org> Signed-off-by: Eric Sunshine <email@example.com> --- Documentation/git-worktree.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt index 544464f949..6ee6ec7982 100644 --- a/Documentation/git-worktree.txt +++ b/Documentation/git-worktree.txt @@ -25,8 +25,9 @@ Manage multiple working trees attached to the same repository. A git repository can support multiple working trees, allowing you to check out more than one branch at a time. With `git worktree add` a new working tree is associated with the repository. This new working tree is called a -"linked working tree" as opposed to the "main working tree" prepared by `git -init` or `git clone`. A repository has one main working tree (if it's not a +"linked working tree" as opposed to the "main working tree" prepared by +linkgit:git-init or linkgit:git-clone. +A repository has one main working tree (if it's not a bare repository) and zero or more linked working trees. When you are done with a linked working tree, remove it with `git worktree remove`. -- 188.8.131.52.gb10cc79966
next prev parent reply other threads:[~2020-08-04 0:56 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-03 5:36 [PATCH 0/4] git-worktree documentation cleanups Eric Sunshine 2020-08-03 5:36 ` [PATCH 1/4] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine 2020-08-03 5:36 ` [PATCH 2/4] git-worktree.txt: consistently use term "working tree" Eric Sunshine 2020-08-03 5:36 ` [PATCH 3/4] git-worktree.txt: fix minor grammatical issues Eric Sunshine 2020-08-03 5:36 ` [PATCH 4/4] git-worktree.txt: make start of new sentence more obvious Eric Sunshine 2020-08-03 16:11 ` [PATCH 0/4] git-worktree documentation cleanups Taylor Blau 2020-08-03 17:14 ` Junio C Hamano 2020-08-03 17:57 ` Martin Ågren 2020-08-03 23:54 ` Eric Sunshine 2020-08-04 0:15 ` Junio C Hamano 2020-08-04 0:55 ` [PATCH v2 0/5] " Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 1/5] git-worktree.txt: employ fixed-width typeface consistently Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 2/5] git-worktree.txt: consistently use term "working tree" Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 3/5] git-worktree.txt: fix minor grammatical issues Eric Sunshine 2020-08-04 0:55 ` [PATCH v2 4/5] git-worktree.txt: make start of new sentence more obvious Eric Sunshine 2020-08-04 0:55 ` Eric Sunshine [this message] 2020-08-04 1:10 ` [PATCH v2 0/5] git-worktree documentation cleanups Taylor Blau 2020-08-04 4:28 ` Martin Ågren 2020-08-04 4:44 ` Eric Sunshine 2020-08-04 5:23 ` Martin Ågren
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 5/5] git-wortkree.txt: link to man pages when citing other Git commands' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).