public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Stephen Boyd <bebarino@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 2/2] ls-tree: migrate to parse-options
Date: Mon, 16 Nov 2009 22:22:00 -0800	[thread overview]
Message-ID: <7vpr7hisc7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1258173248-31059-3-git-send-email-bebarino@gmail.com

Thanks.

As parse-options infrastructure gives much better per-option help text,
there is not much point to keep the list of options that can go stale
in the usage text.

I'd squash this to yours.  Ok?

---
 builtin-ls-tree.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/builtin-ls-tree.c b/builtin-ls-tree.c
index 04408df..14a913a 100644
--- a/builtin-ls-tree.c
+++ b/builtin-ls-tree.c
@@ -24,7 +24,7 @@ static int chomp_prefix;
 static const char *ls_tree_prefix;
 
 static const  char * const ls_tree_usage[] = {
-	"git ls-tree [-d] [-r] [-t] [-l | --long] [-z] [--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev[=<n>]] <tree-ish> [path...]",
+	"git ls-tree <options> <tree-ish> [path...]",
 	NULL
 };
 
-- 
1.6.5.3.283.g4b054

  reply	other threads:[~2009-11-17  6:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-14  4:34 [PATCH 0/2] Migrate ls-tree to parse-opts Stephen Boyd
2009-11-14  4:34 ` [PATCH 1/2] t3101: test more ls-tree options Stephen Boyd
2009-11-17  6:21   ` Junio C Hamano
2009-11-17  6:26     ` Stephen Boyd
2009-11-14  4:34 ` [PATCH 2/2] ls-tree: migrate to parse-options Stephen Boyd
2009-11-17  6:22   ` Junio C Hamano [this message]
2009-11-17  6:28     ` Stephen Boyd
2009-11-17  7:02     ` Stephen Boyd
2009-11-18 22:19       ` Junio C Hamano
2009-11-18 23:10         ` Thiago Farina

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=7vpr7hisc7.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox$(echo .)com \
    --cc=bebarino@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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