status letters consistency in log and ls-files

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

status letters consistency in log and ls-files

From: Leo Razoumov <hidden>
Date: 2016-06-15 22:45:24

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--

Re: status letters consistency in log and ls-files

From: Jeff King <hidden>
Date: 2016-06-15 22:45:24

On Fri, Sep 26, 2008 at 02:28:50PM -0400, Leo Razoumov wrote:
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?
I think this is rooted in historical reasons. Unfortunately, I don't
think it is possible to reconcile the two outputs at this point, as we
would be breaking any scripts which use the tools.

Out of curiosity, is there a script you are writing or some workflow you
have where you see the output of both? Or did you just notice this while
exploring git?

I ask because there may be a way to alter your workflow to always use
one tool.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help