user/sven/git.git/lib, branch gitgui-0.9.1

git-gui: Make commit log messages end with a newline

2007-12-30T02:03:55Z

Concatenating commit log messages from multiple commits works better when all of the commits end with a clean line break. Its good to be strict in what you create, and lenient in what you accept, and since we're creating here, we should always try to Do The Right Thing(tm). Signed-off-by: Bernt Hansen Signed-off-by: Shawn O. Pearce

git-gui: Handle file mode changes (644->755) in diff viewer

2007-12-14T06:51:22Z

Johannes Sixt pointed out the diff headers "old mode ..." and "new mode ..." were not being parsed properly by git-gui. We now include them in the diff viewer for a file. Signed-off-by: Shawn O. Pearce

git-gui: Improve the application icon on Windows.

2007-12-03T04:05:10Z

Previusly, there was only a 16x16 image, which looked very distorted. Here we add a 32x32 version, and also make the image sharper. Signed-off-by: Johannes Sixt Signed-off-by: Shawn O. Pearce

git-gui: fix a typo in lib/commit.tcl

2007-11-22T21:02:09Z

Signed-off-by: Michele Ballabio Signed-off-by: Shawn O. Pearce

Merge branch 'maint'

2007-10-23T22:50:19Z

* maint: git-gui: Make sure we get errors from git-update-index Conflicts: lib/index.tcl

git-gui: Make sure we get errors from git-update-index

2007-10-23T22:49:27Z

I'm seeing a lot of silent failures from git-update-index on Windows and this is leaving the index.lock file intact, which means users are later unable to perform additional operations. When the index is locked behind our back and we are unable to use it we may need to allow the user to delete the index lock and try again. However our UI state is probably not currect as we have assumed that some changes were applied but none of them actually did. A rescan is the easiest (in code anyway) solution to correct our UI to show what the index really has (or doesn't have). Signed-off-by: Shawn O. Pearce

Merge branch 'maint'

2007-10-21T00:43:36Z

* maint: git-gui: Don't display CR within console windows git-gui: Handle progress bars from newer gits git-gui: Correctly report failures from git-write-tree Conflicts: lib/commit.tcl lib/console.tcl

git-gui: Don't display CR within console windows

2007-10-21T00:42:01Z

Git progress bars from tools like git-push and git-fetch use CR to skip back to the start of the current line and redraw it with an updated progress. We were doing this in our Tk widget but had failed to skip the CR, which Tk doesn't draw well. Signed-off-by: Shawn O. Pearce

git-gui: Handle progress bars from newer gits

2007-10-21T00:36:27Z

Post Git 1.5.3 a new style progress bar has been introduced that uses only one line rather than two. The formatting of the completed and total section is also slightly different so we must adjust our regexp to match. Unfortunately both styles are in active use by different versions of Git so we need to look for both. Signed-off-by: Shawn O. Pearce

git-gui: Correctly report failures from git-write-tree

2007-10-20T05:42:01Z

If git-write-tree fails (such as if the index file is currently locked and it wants to write to it) we were not getting the error message as $tree_id was always the empty string so we shortcut through the catch and never got the output from stderr. Signed-off-by: Shawn O. Pearce