| commit | c17c1751339bbb13e8927b0e98274cfee406821e | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 2 Jun 2007 19:13:35 +0000 (2 15:13 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 6 Jun 2007 05:26:50 +0000 (6 01:26 -0400) | ||
| tree | 5ff805a4d8e678bb4063696784ce97a361c2f208 | treesnapshot (tar.gz zip) |
| parent | b61101579fdc647c14a54105a361b549a97c09a4 | commitdiff |
git-gui: Better document our blame variables
The array variable "order" used to be used to tell us in what
order each commit was received in. Recent changes have removed
that need for an ordering and the "order" array is now just a
boolean 'do we have that commit yet' flag.
The colors were moved to fields, so they appear inside of the
blame viewer instance. This keeps two different concurrently
running blame viewers from stepping on each other's ordering
of the colors in group_colors.
Most of the other fields were moved around a little bit so
that they are organized by major category and value lifespan.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
The array variable "order" used to be used to tell us in what
order each commit was received in. Recent changes have removed
that need for an ordering and the "order" array is now just a
boolean 'do we have that commit yet' flag.
The colors were moved to fields, so they appear inside of the
blame viewer instance. This keeps two different concurrently
running blame viewers from stepping on each other's ordering
of the colors in group_colors.
Most of the other fields were moved around a little bit so
that they are organized by major category and value lifespan.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| lib/blame.tcl | diffblobblamehistory |