All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Des Preston via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Des Preston <despreston@gmail.com>, Des Preston <despreston@gmail.com>
Subject: [PATCH] worktree: include repair cmd in usage
Date: Fri, 25 Mar 2022 18:05:04 +0000	[thread overview]
Message-ID: <pull.1188.git.1648231504463.gitgitgadget@gmail.com> (raw)

From: Des Preston <despreston@gmail.com>

The worktree repair command was not added to the usage menu for the
worktree command. This commit adds the usage of 'worktree repair'
according to the existing docs.

Signed-off-by: Des Preston <despreston@gmail.com>
---
    worktree: include repair cmd in usage
    
    I'm working on an extension for the github CLI (github.com/cli/cli) to
    make it easier to create and manage worktrees using Github info
    (github.comm/despreston/gh-worktree). I noticed there was a worktree
    command that wasn't showing up in the usage menu git worktree -h.
    
    Signed-off-by: Des Preston despreston@gmail.com

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1188%2Fdespreston%2Fworktree-usage-repair-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1188/despreston/worktree-usage-repair-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1188

 builtin/worktree.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/builtin/worktree.c b/builtin/worktree.c
index 2838254f7f2..8682ff4c417 100644
--- a/builtin/worktree.c
+++ b/builtin/worktree.c
@@ -22,6 +22,7 @@ static const char * const worktree_usage[] = {
 	N_("git worktree move <worktree> <new-path>"),
 	N_("git worktree prune [<options>]"),
 	N_("git worktree remove [<options>] <worktree>"),
+	N_("git worktree repair [<path>]"),
 	N_("git worktree unlock <path>"),
 	NULL
 };

base-commit: 4c53a8c20f8984adb226293a3ffd7b88c3f4ac1a
-- 
gitgitgadget

             reply	other threads:[~2022-03-25 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 18:05 Des Preston via GitGitGadget [this message]
2022-03-25 19:55 ` [PATCH] worktree: include repair cmd in usage Eric Sunshine
2022-03-28 20:47 ` [PATCH v2 0/2] " Des Preston via GitGitGadget
2022-03-28 20:47   ` [PATCH v2 1/2] " Des Preston via GitGitGadget
2022-03-28 20:47   ` [PATCH v2 2/2] worktree: accept multiple paths Des Preston via GitGitGadget
2022-03-29  1:00     ` Junio C Hamano
2022-03-29  3:00       ` Desmond Preston
2022-03-29 16:01         ` Junio C Hamano
2022-03-29 18:36           ` Eric Sunshine

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.1188.git.1648231504463.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=despreston@gmail.com \
    --cc=git@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.