Understanding the diff output in gitk when comparing a commit with working tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello everyone,

in gitk one can compare commits by selecting one commit, then right click on another commit and use the different diff options in the context menu. That works great!
I found that when comparing a commit with those changes made in the working tree, I don’t understand the following observations I made in the diff output for _some_ files:

- the diff output is not colored in red and green for additions and removals, but in red and bold black (still preceded with “++”, “+-“, “--“ and so on)
- some files show no differences, but an external diff shows that those differences are there
- the index of the diff shows an output like mentioned in the “combined diff” format (see https://git-scm.com/docs/diff-format#_combined_diff_format), and looks like “index NUMBER,NUMBER..NUMER”

Other files show up in a “normal” way; as a diff with red and green highlighted lines for additions and removals and no empty file diffs.

To reproduce this make some more changes in the working tree of a git repo. Then compare an older commit with the working tree in gitk and search for my observations in the diff output.

Can someone please explain me why all this happens?

Best wishes
Tobias



-------------------------------------------------------------------------------------------------
imperial-Werke oHG, Sitz Bünde, Registergericht Bad Oeynhausen - HRA 4825




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux