From: "Des Preston via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Des Preston <despreston@gmail.com>
Subject: [PATCH v2 0/2] worktree: include repair cmd in usage
Date: Mon, 28 Mar 2022 20:47:04 +0000 [thread overview]
Message-ID: <pull.1188.v2.git.1648500426.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1188.git.1648231504463.gitgitgadget@gmail.com>
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
Des Preston (2):
worktree: include repair cmd in usage
worktree: accept multiple paths
builtin/worktree.c | 1 +
1 file changed, 1 insertion(+)
base-commit: 4c53a8c20f8984adb226293a3ffd7b88c3f4ac1a
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1188%2Fdespreston%2Fworktree-usage-repair-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1188/despreston/worktree-usage-repair-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/1188
Range-diff vs v1:
1: e0bfbfd5320 = 1: e0bfbfd5320 worktree: include repair cmd in usage
-: ----------- > 2: 1df005a4ef1 worktree: accept multiple paths
--
gitgitgadget
next prev parent reply other threads:[~2022-03-28 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 18:05 [PATCH] worktree: include repair cmd in usage Des Preston via GitGitGadget
2022-03-25 19:55 ` Eric Sunshine
2022-03-28 20:47 ` Des Preston via GitGitGadget [this message]
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.v2.git.1648500426.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=despreston@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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.