From: "Julien Richard via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>,
Julien Richard <julien.richard@ubisoft.com>,
Julien Richard <jairbubbles@hotmail.com>,
Julien Richard <julien.richard@ubisoft.com>
Subject: [PATCH v2] doc: 'T' status code for git status
Date: Wed, 09 Dec 2020 19:12:07 +0000 [thread overview]
Message-ID: <pull.930.v2.git.git.1607541127701.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.930.git.git.1607501616914.gitgitgadget@gmail.com>
From: Julien Richard <julien.richard@ubisoft.com>
Git status can return 'T' status code which stands for "typechange", fixing the documentation accordingly.
Signed-off-by: Julien Richard <jairbubbles@hotmail.com>
---
Document 'T' status code for git status
Git status can return 'T' status code which stands for "typechange". I
can't document more the behavior but it would have helped me a lot to
see that line in the documentation so I guess it can help others too.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-930%2Fjairbubbles%2FgitStatusTypeChangeCode-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-930/jairbubbles/gitStatusTypeChangeCode-v2
Pull-Request: https://github.com/git/git/pull/930
Range-diff vs v1:
1: ee106c427a0 ! 1: 8511a2d4f10 doc: 'T' status code for git status
@@ Documentation/git-status.txt: codes can be interpreted as follows:
* 'R' = renamed
* 'C' = copied
* 'U' = updated but unmerged
-+* 'T' = type changed
++* 'T' = type changed (e.g. a symbolic link becoming a file)
Ignored files are not listed, unless `--ignored` option is in effect,
in which case `XY` are `!!`.
Documentation/git-status.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index 7731b45f078..21c406a812c 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -197,6 +197,7 @@ codes can be interpreted as follows:
* 'R' = renamed
* 'C' = copied
* 'U' = updated but unmerged
+* 'T' = type changed (e.g. a symbolic link becoming a file)
Ignored files are not listed, unless `--ignored` option is in effect,
in which case `XY` are `!!`.
base-commit: 3a0b884caba2752da0af626fb2de7d597c844e8b
--
gitgitgadget
prev parent reply other threads:[~2020-12-09 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 8:13 [PATCH] doc: 'T' status code for git status Julien Richard via GitGitGadget
2020-12-09 17:37 ` Jeff King
2020-12-09 18:01 ` Julien Richard
2020-12-09 18:35 ` Jeff King
2020-12-09 20:26 ` Junio C Hamano
2020-12-09 20:56 ` Julien Richard
2020-12-09 21:32 ` Jeff King
2020-12-10 0:47 ` Junio C Hamano
2020-12-09 19:12 ` Julien Richard via GitGitGadget [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=pull.930.v2.git.git.1607541127701.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=jairbubbles@hotmail.com \
--cc=julien.richard@ubisoft.com \
--cc=peff@peff.net \
/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.