From: Jens Lehmann <Jens.Lehmann@web.de>
To: Nicolas Morey-Chaisemartin <nmorey@kalray.eu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation/git-submodule.txt: Document the new 'U' prefix of git submodule status on submodules with merge conflicts
Date: Tue, 22 Mar 2011 20:23:34 +0100 [thread overview]
Message-ID: <4D88F736.209@web.de> (raw)
In-Reply-To: <4D886432.6060007@kalray.eu>
Am 22.03.2011 09:56, schrieb Nicolas Morey-Chaisemartin:
> Signed-off-by: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
> ---
> Documentation/git-submodule.txt | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
> index 3a5aa01..1a16ff6 100644
> --- a/Documentation/git-submodule.txt
> +++ b/Documentation/git-submodule.txt
> @@ -101,9 +101,10 @@ status::
> currently checked out commit for each submodule, along with the
> submodule path and the output of 'git describe' for the
> SHA-1. Each SHA-1 will be prefixed with `-` if the submodule is not
> - initialized and `+` if the currently checked out submodule commit
> + initialized, `+` if the currently checked out submodule commit
> does not match the SHA-1 found in the index of the containing
> - repository. This command is the default command for 'git submodule'.
> + repository and `U` if the submodule has merge conflicts.
Nit: The submodule doesn't have merge conflicts, the superproject does.
Maybe something like this (but I suspect a native speaker can come up
with something better ;-):
+ repository and `U` if a merge of the submodule commits produced
+ a conflict.
> + This command is the default command for 'git submodule'.
> +
> If '--recursive' is specified, this command will recurse into nested
> submodules, and show their status as well.
And I'd propose to squash this one into the first patch, as it documents
the behavior change done there.
prev parent reply other threads:[~2011-03-22 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51d033dc2978d62164dcb76b679bb7ebd9bc1802.1300784018.git.nmorey@kalray.eu>
2011-03-22 8:56 ` [PATCH 2/2] Documentation/git-submodule.txt: Document the new 'U' prefix of git submodule status on submodules with merge conflicts Nicolas Morey-Chaisemartin
2011-03-22 19:23 ` Jens Lehmann [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=4D88F736.209@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=nmorey@kalray.eu \
/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.