| commit | 93a79912055dfc0cbdc974e98c705bc75950862a | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 21 Nov 2006 03:17:15 +0000 (20 22:17 -0500) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 21 Nov 2006 05:22:34 +0000 (21 00:22 -0500) | ||
| tree | e0ac952ef9fe6a8bcd6975939af290ca829c9334 | treesnapshot (tar.gz zip) |
| parent | 21d7744fbc98b526bc00138fce287565df2c0075 | commitdiff |
git-gui: Reworded verify console title.
It would be something of a disservice to our users if we refer to
fsck-objects as "verify". So instead we call it fsck-objects in
the console title, and indicate that's how we are verifying the
object database.
We probably should call our menu option "fsck-objects" or similar
but I really do think that "Verify Database" more accurately describes
the action then "fsck-objects" does, especially to users who aren't
file system developers.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
It would be something of a disservice to our users if we refer to
fsck-objects as "verify". So instead we call it fsck-objects in
the console title, and indicate that's how we are verifying the
object database.
We probably should call our menu option "fsck-objects" or similar
but I really do think that "Verify Database" more accurately describes
the action then "fsck-objects" does, especially to users who aren't
file system developers.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui | diffblobblamehistory |