git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James <purpleidea@gmail.com>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] Add --recursive flag to git bash completion script.
Date: Sun, 08 Mar 2015 20:00:16 -0400	[thread overview]
Message-ID: <1425859216.8244.40.camel@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 205 bytes --]

This is a patch to add a much needed option to the bash completion
script. I'm not subscribed to this list, so please include me in your
reply if you'd like me to see your response.

Thanks,
James


[-- Attachment #1.2: completion-recursive.patch --]
[-- Type: text/x-patch, Size: 775 bytes --]

From ca976de5bfeccc9bd69c22183f82b9d1e59d2547 Mon Sep 17 00:00:00 2001
From: James Shubin <james@shubin.ca>
Date: Sun, 8 Mar 2015 19:57:17 -0400
Subject: [PATCH] Add --recursive flag to git bash completion script.

This flag was missing from the list, and I use it quite often :)

Signed-off-by: James Shubin <james@shubin.ca>
---
 contrib/completion/git-completion.bash | 1 +
 1 file changed, 1 insertion(+)

diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
index c21190d..6cb7ff5 100644
--- a/contrib/completion/git-completion.bash
+++ b/contrib/completion/git-completion.bash
@@ -1090,6 +1090,7 @@ _git_clone ()
 			--no-hardlinks
 			--shared
 			--reference
+			--recursive
 			--quiet
 			--no-checkout
 			--bare
-- 
2.1.0


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-03-09  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09  0:00 James [this message]
2015-03-09 10:43 ` [PATCH] Add --recursive flag to git bash completion script Thomas Ferris Nicolaisen
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 21:00 James

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=1425859216.8244.40.camel@gmail.com \
    --to=purpleidea@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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 NNTP newsgroup(s).