From: "Leo Razoumov" <slonik.az@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: status letters consistency in log and ls-files
Date: Fri, 26 Sep 2008 14:28:50 -0400 [thread overview]
Message-ID: <ee2a733e0809261128h4c50d27bq3942bd1b3b66d3ee@mail.gmail.com> (raw)
Hi Everyone,
I am new yo git and there are few things I find quite odd. For example,
command "git log --name-status" uses the following letters to indicate
file's status
A -- Added
B -- have had their pairing Broken
C -- Copied
D -- Deleted
M -- Modified
R -- Renamed
T -- Type changed (mode, time stamp)
U -- Unmerged
X -- Unknown
At the same time command "git ls-files -v" use different letters to
indicate the same
H -- cached
M -- unmerged
R -- removed/deleted
C -- modified/changed
K -- to be killed
? -- other
So, depending on which of the commands above are used status "R" could
mean either Renamed or Removed, "M" is either Modified or unMerged,
"C" is either Copied or Changed.
Is it possible to make it consistent across related commands?
--Leo--
next reply other threads:[~2008-09-26 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 18:28 Leo Razoumov [this message]
2008-09-26 22:45 ` status letters consistency in log and ls-files Jeff King
[not found] ` <ee2a733e0809261624y72dcfb8fw7910feb2542f501c@mail.gmail.com>
[not found] ` <20080927002949.GA25586@coredump.intra.peff.net>
2008-09-27 3:20 ` Leo Razoumov
2008-09-27 3:30 ` Jeff King
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=ee2a733e0809261128h4c50d27bq3942bd1b3b66d3ee@mail.gmail.com \
--to=slonik.az@gmail.com \
--cc=git@vger.kernel.org \
/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).