From: Marc Branchaud <marcnarc@xiplink.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Nikolai Weibull <now@bitwi.se>
Subject: Re: [PATCH] Documentation/submodule: add command references and update options
Date: Tue, 26 Jul 2011 14:54:03 -0400 [thread overview]
Message-ID: <4E2F0D4B.2000209@xiplink.com> (raw)
In-Reply-To: <4E2F0AF7.2070306@web.de>
On 11-07-26 02:44 PM, Jens Lehmann wrote:
> Am 25.07.2011 22:30, schrieb Junio C Hamano:
>> Jens Lehmann <Jens.Lehmann@web.de> writes:
>>
>>> @@ -140,11 +146,14 @@ summary::
>>> Show commit summary between the given commit (defaults to HEAD) and
>>> working tree/index. For a submodule in question, a series of commits
>>> in the submodule between the given super project commit and the
>>> - index or working tree (switched by --cached) are shown. If the option
>>> - --files is given, show the series of commits in the submodule between
>>> + index or working tree (switched by '--cached') are shown. If the option
>>> + '--files' is given, show the series of commits in the submodule between
>>> the index of the super project and the working tree of the submodule
>>> - (this option doesn't allow to use the --cached option or to provide an
>>> + (this option doesn't allow to use the '--cached' option or to provide an
>>> explicit commit).
>>> ++
>>> +Using the '--submodule=log' option with linkgit:git-diff[1] will provide the
>>> +same information.
>>
>> I am not a huge fan of these extra paragraphs, especially in reality it is
>> not "provide the same" but "the same and a lot of other".
>>
>> I dunno.
>
> I added them because in a discussion with Marc it became apparent that users
> can't learn about what diff and status can do for them by checking the submodule
> man-page. But you are right about "the same and a lot of other", I will update
> the wording of those paragraphs.
>
> Maybe someone else has a better idea how to inform users that git diff and
> status can tell you a lot (and sometimes even more than the submodule script)
> about the state submodules are in?
I thought the brief sentence in the patch was fine, myself.
M.
prev parent reply other threads:[~2011-07-26 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 19:00 [PATCH] Documentation/submodule: add command references and update options Jens Lehmann
2011-07-25 20:30 ` Junio C Hamano
2011-07-26 18:44 ` Jens Lehmann
2011-07-26 18:54 ` Marc Branchaud [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=4E2F0D4B.2000209@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=now@bitwi.se \
/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.