All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: catalin.marinas@gmail.com
Cc: git@vger.kernel.org
Subject: [StGit PATCH revised] Remove add/applied/unapplied bash completion entries
Date: Sun, 31 Aug 2008 05:30:57 +0900	[thread overview]
Message-ID: <48B9AE01.1010804@ruby.dti.ne.jp> (raw)
In-Reply-To: <48B9A37B.4060001@ruby.dti.ne.jp>

These commands are not available any more.

Signed-off-by: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
---
Shinya Kuribayashi wrote:
> "stg add" was dropped several months ago.

Hm, I should have removed applied/unapplied entries also.

thanks,

  Shinya

 contrib/stgit-completion.bash |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/contrib/stgit-completion.bash b/contrib/stgit-completion.bash
index 1867e6b..ac868e7 100644
--- a/contrib/stgit-completion.bash
+++ b/contrib/stgit-completion.bash
@@ -11,8 +11,6 @@
 #         . ~/.stgit-completion.bash
 
 _stg_commands="
-    add
-    applied
     branch
     delete
     diff
@@ -51,7 +49,6 @@ _stg_commands="
     status
     sync
     top
-    unapplied
     uncommit
     unhide
 "
@@ -264,7 +261,6 @@ _stg ()
         # working-copy commands
         diff)   _stg_patches_options $command _applied_patches "-r --range" ;;
 	resolved) _complete_files $command "$(_conflicting_files)" ;;
-	add)	_complete_files $command "$(_unknown_files)" ;;
 #	rm)	_complete_files $command "$(_known_files)" ;;
 	# commands that usually raher accept branches
 	branch) _complete_branch $command _all_branches ;;

  reply	other threads:[~2008-08-30 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30 19:46 [StGit PATCH] Remove 'add' command entries from stgit-completion.bash Shinya Kuribayashi
2008-08-30 20:30 ` Shinya Kuribayashi [this message]
2008-09-05 17:16   ` [StGit PATCH rev3] contrib/stgit-completion.bash: Remove add/applied/cp/rm/unapplied Shinya Kuribayashi
2008-09-06  6:18     ` Karl Hasselström
2008-09-06 14:28     ` Karl Hasselström

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=48B9AE01.1010804@ruby.dti.ne.jp \
    --to=skuribay@ruby.dti.ne.jp \
    --cc=catalin.marinas@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.