diff options
author | Shawn O. Pearce <spearce@spearce.org> | 2006-11-20 22:17:15 -0500 |
---|---|---|
committer | Shawn O. Pearce <spearce@spearce.org> | 2006-11-21 00:22:34 -0500 |
commit | 93a79912055dfc0cbdc974e98c705bc75950862a (patch) | |
tree | e0ac952ef9fe6a8bcd6975939af290ca829c9334 /git-gui | |
parent | git-gui: Don't save amended commit message buffer. (diff) | |
download | tgif-93a79912055dfc0cbdc974e98c705bc75950862a.tar.xz |
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>
Diffstat (limited to 'git-gui')
-rwxr-xr-x | git-gui | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -1947,7 +1947,8 @@ proc do_gitk {} { } proc do_repack {} { - set w [new_console "repack" "Repacking the object database"] + set w [new_console {repack} \ + {Repacking the object database}] set cmd [list git repack] lappend cmd -a lappend cmd -d @@ -1955,7 +1956,8 @@ proc do_repack {} { } proc do_fsck_objects {} { - set w [new_console "verify" "Verifying the object database"] + set w [new_console {fsck-objects} \ + {Verifying the object database with fsck-objects}] set cmd [list git fsck-objects] lappend cmd --full lappend cmd --cache |