diff options
author | Shawn O. Pearce <spearce@spearce.org> | 2007-06-06 03:22:22 -0400 |
---|---|---|
committer | Shawn O. Pearce <spearce@spearce.org> | 2007-06-06 03:22:22 -0400 |
commit | 0f32da53df706220e7392a29d8e462b57345df3d (patch) | |
tree | c409ed5a39120845d9bcce11b6845dd16bb429e0 /usage.c | |
parent | git-gui: Improve our labeling of blame annotation types (diff) | |
download | tgif-0f32da53df706220e7392a29d8e462b57345df3d.tar.xz |
git-gui: Favor the original annotations over the recent ones
Usually when you are looking at blame annotations for a region of
a file you are more interested in why something was originally
done then why it is here now. This is because most of the time
when we get original annotation data we are looking at a simple
refactoring performed to better organize code, not to change its
semantic meaning or function. Reorganizations are sometimes of
interest, but not usually.
We now show the original commit data first in the tooltip. This
actually looks quite nice as the original commit will usually have an
author date prior to the current (aka move/copy) annotation's commit,
so the two commits will now tend to appear in chronological order.
I also found myself to always be clicking on the line of interest
in the file column but I always wanted the original tracking data
and not the move/copy data. So I changed our default commit from
$asim_data (the simple move/copy annotation) to the more complex
$amov_data (the -M -C -C original annotation).
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 'usage.c')
0 files changed, 0 insertions, 0 deletions