git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Imran M Yousuf" <imyousuf@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, "Imran M Yousuf" <imyousuf@smartitengineering.com>
Subject: Re: [PATCH] git-submodule.sh: Add Long Usage instead of simple usage
Date: Mon, 5 May 2008 15:07:08 +0600	[thread overview]
Message-ID: <7bfdc29a0805050207l3ef55648u9a8cbd6e57711e0c@mail.gmail.com> (raw)
In-Reply-To: <1209977051-25896-1-git-send-email-imyousuf@gmail.com>

Sorry for the inconvenience, but please ignore this patch as it was
not generated with -n and version number :(.

- best regards,

Imran

On Mon, May 5, 2008 at 2:44 PM,  <imyousuf@gmail.com> wrote:
> From: Imran M Yousuf <imyousuf@smartitengineering.com>
>
>  With the already available commands the synopsis is quite hard to
>  read; thus converted it to Long usage instead. In process also
>  updated the file comment.
>
>  Signed-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>
>  ---
>   git-submodule.sh |   13 +++++++++----
>   1 files changed, 9 insertions(+), 4 deletions(-)
>
>  diff --git a/git-submodule.sh b/git-submodule.sh
>  index ce0f00c..a5ee2e5 100755
>  --- a/git-submodule.sh
>  +++ b/git-submodule.sh
>  @@ -1,12 +1,17 @@
>   #!/bin/sh
>   #
>  -# git-submodules.sh: add, init, update or list git submodules
>  +# git-submodules.sh: add, init, update, summary or status git submodules
>   #
>   # Copyright (c) 2007 Lars Hjemli
>
>  -USAGE="[--quiet] [--cached] \
>  -[add <repo> [-b branch]|status|init|update|summary [-n|--summary-limit <n>] [<commit>]] \
>  -[--] [<path>...]"
>  +USAGE="<command> <options>
>  +Use $0 -h for more details"
>  +# Did not use '\' at the end of the lines to ensure that each synopsis
>  +# are in a separate line
>  +LONG_USAGE="$0 add [-q|--quiet] [-b|--branch branch] <repository> [<path>]
>  +$0 [status] [-q|--quiet] [-c|--cached] [--] [<path>...]
>  +$0 init|update [-q|--quiet] [--] [<path>...]
>  +$0 summary [--cached] [-n|--summary-limit <n>] [<commit>]"
>   OPTIONS_SPEC=
>   . git-sh-setup
>   require_work_tree
>  --
>  1.5.4.2
>
>

      parent reply	other threads:[~2008-05-05  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  8:44 [PATCH] git-submodule.sh: Add Long Usage instead of simple usage imyousuf
2008-05-05  8:44 ` [PATCH] git-submodule.sh: Add recurse subcommand with basic options imyousuf
2008-05-05  8:44   ` [PATCH] git-submodule.sh: Add Custom argument input support to git submodule recurse subcommand imyousuf
2008-05-05  8:44     ` [PATCH] git-submodule.sh: Add pre command argument " imyousuf
2008-05-05  8:44       ` [PATCH] Documentation/git-submodule.txt: Add documentation for the " imyousuf
2008-05-05  9:07         ` Imran M Yousuf
2008-05-05  9:07       ` [PATCH] git-submodule.sh: Add pre command argument to git submodule " Imran M Yousuf
2008-05-05  9:07     ` [PATCH] git-submodule.sh: Add Custom argument input support " Imran M Yousuf
2008-05-05  9:08   ` [PATCH] git-submodule.sh: Add recurse subcommand with basic options Imran M Yousuf
2008-05-05  9:07 ` Imran M Yousuf [this message]

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=7bfdc29a0805050207l3ef55648u9a8cbd6e57711e0c@mail.gmail.com \
    --to=imyousuf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=imyousuf@smartitengineering.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).