From: "Imran M Yousuf" <imyousuf@gmail.com>
To: "Lars Hjemli" <lh@elementstorage.no>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Simplified the invocation of command action in submodule
Date: Thu, 10 Jan 2008 09:05:20 +0600 [thread overview]
Message-ID: <7bfdc29a0801091905k1ef9285em170b26a332a30535@mail.gmail.com> (raw)
In-Reply-To: <8c5c35580801090224l1e30df6cw5d3fefe99c0cdd7@mail.gmail.com>
On Jan 9, 2008 4:24 PM, Lars Hjemli <lh@elementstorage.no> wrote:
> On Jan 9, 2008 10:51 AM, Imran M Yousuf <imyousuf@gmail.com> wrote:
> > On Jan 9, 2008 2:59 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> > >
> > > - Previously, passing --cached to add, init, or update was an error, now
> > > it is not.
> >
> > The usage statement and this behaviour is rather contradicting. The
> > usage says that --cached can be used with all commands; so I am not
> > sure whether using --cached with add should be an error or not. IMHO,
> > if the previous implementation was right than the USAGE has to be
> > changed, and if the previous implementation was incorrect, than if the
> > default command is set to status than current implementation is right.
> >
> > I would like to get comment on this until I fix the patch and resend it.
>
> --cached only makes sense for the status subcommand, so the
> usage/manpage probably should have looked like this (except for the
> whitespace mangling...):
>
> diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
> index cffc6d4..331e806 100644
> --- a/Documentation/git-submodule.txt
> +++ b/Documentation/git-submodule.txt
> @@ -10,7 +10,10 @@ SYNOPSIS
> --------
> [verse]
> 'git-submodule' [--quiet] [-b branch] add <repository> [<path>]
> -'git-submodule' [--quiet] [--cached] [status|init|update] [--] [<path>...]
> +'git-submodule' [--quiet] [--cached] [status] [--] [<path>...]
> +'git-submodule' [--quiet] init [--] [<path>...]
> +'git-submodule' [--quiet] update [--] [<path>...]
> +
>
This change makes a lot sense. Thus I will make sure that it is used
in this manner :). Thanks a lot for clarifying it Lars. I wanted to
know what is the purpose of '--'? If it is simply meant to be a
separator than fine; else I would be grateful if you would please
explain its purpose, so that I do not again implement wrongly :).
>
> COMMANDS
> --
> 1.5.3.7.1141.g4eb39
>
--
Imran M Yousuf
prev parent reply other threads:[~2008-01-10 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 3:59 [PATCH] Simplified the invocation of command action in submodule imyousuf
2008-01-09 8:19 ` Junio C Hamano
2008-01-09 8:23 ` Imran M Yousuf
2008-01-09 8:59 ` Johannes Sixt
2008-01-09 9:07 ` Imran M Yousuf
2008-01-09 9:15 ` Johannes Sixt
2008-01-09 9:51 ` Imran M Yousuf
2008-01-09 10:01 ` Johannes Sixt
2008-01-09 10:06 ` Imran M Yousuf
2008-01-09 10:27 ` Junio C Hamano
2008-01-09 10:24 ` Lars Hjemli
2008-01-10 3:05 ` 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=7bfdc29a0801091905k1ef9285em170b26a332a30535@mail.gmail.com \
--to=imyousuf@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=lh@elementstorage.no \
/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).