From: Junio C Hamano <gitster@pobox.com>
To: "David Cantrell via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, David Cantrell <david@cantrell.org.uk>
Subject: Re: [PATCH v2 0/2] Improved bash tab completion for 'git restore' - adds support for auto-completing filenames
Date: Tue, 15 Mar 2022 04:23:51 -0700 [thread overview]
Message-ID: <xmqq8rtbh320.fsf@gitster.g> (raw)
In-Reply-To: pull.1227.v2.git.git.1647305547.gitgitgadget@gmail.com
"David Cantrell via GitGitGadget" <gitgitgadget@gmail.com> writes:
> This adds tab-completion of filenames to the bash completions for git
> restore.
>
> David Cantrell (2):
> tab completion of filenames for 'git restore'
> if a file has been staged we don't want to list it
Why two patches? The second separate patch makes the topic look as
if "oops, the first step designed a wrong behaviour and here is a
brown paper bag fix-up".
next prev parent reply other threads:[~2022-03-15 11:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 21:07 [PATCH] tab completion of filenames for 'git restore' David Cantrell via GitGitGadget
2022-03-13 6:45 ` Junio C Hamano
2022-03-14 23:45 ` David Cantrell
2022-03-15 10:23 ` Junio C Hamano
2022-03-15 0:52 ` [PATCH v2 0/2] Improved bash tab completion for 'git restore' - adds support for auto-completing filenames David Cantrell via GitGitGadget
2022-03-15 0:52 ` [PATCH v2 1/2] tab completion of filenames for 'git restore' David Cantrell via GitGitGadget
2022-03-15 0:52 ` [PATCH v2 2/2] if a file has been staged we don't want to list it David Cantrell via GitGitGadget
2022-03-16 11:45 ` Bagas Sanjaya
2022-03-15 11:23 ` Junio C Hamano [this message]
2022-03-15 16:27 ` [PATCH v2 0/2] Improved bash tab completion for 'git restore' - adds support for auto-completing filenames Junio C Hamano
2022-03-15 22:13 ` [PATCH v3] tab completion of filenames for 'git restore' David Cantrell via GitGitGadget
2022-03-16 0:44 ` Junio C Hamano
2022-03-17 22:16 ` David Cantrell
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=xmqq8rtbh320.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=david@cantrell.org.uk \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.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.