git/lib/commit.tcl, branch gitgui-0.19.0

git-gui: remove .git/CHERRY_PICK_HEAD after committing

2012-09-17T10:59:05Z

Adding _git_ps1() to one's bash prompt displays various repo status info after each command. After committing a git cherry-pick -n using git-gui, the prompt still contains the "|CHERRY-PICKING" flag. Delete the file causing this flag when cleaning up. Signed-off-by: Beat Bolli Signed-off-by: Pat Thoyts

git-gui: Fix a loose/lose mistake

2012-09-17T10:53:37Z

Acked-by: Junio C Hamano Signed-off-by: Beat Bolli Signed-off-by: Pat Thoyts

git-gui: don't warn for detached head when rebasing

2011-11-05T00:39:04Z

Signed-off-by: Bert Wesarg Signed-off-by: Pat Thoyts

git-gui: make config gui.warndetachedcommit a boolean

2011-11-05T00:39:03Z

Signed-off-by: Bert Wesarg Signed-off-by: Pat Thoyts

git-gui: warn when trying to commit on a detached head

2011-05-20T21:49:15Z

The commandline is already warning when checking out a detached head. Since the only thing thats potentially dangerous is to create commits on a detached head lets warn in case the user is about to do that. Signed-off-by: Heiko Voigt Signed-off-by: Pat Thoyts

git-gui: learn more type change states

2011-01-28T00:16:50Z

Support the following states with type change in git-gui: AT, MT, TD, TM Signed-off-by: Bert Wesarg Signed-off-by: Pat Thoyts

git-gui: remove 'no such variable' for s error when encounter unknown file states

2011-01-28T00:16:46Z

$s will be referenced in the error message. Which was broken since "git-gui: Automatically update-index all included files before commit" (bbe3b3b, 2006-11-16). Signed-off-by: Bert Wesarg Signed-off-by: Pat Thoyts

git-gui: When calling post-commit hook wrong variable was cleared.

2009-04-05T19:45:40Z

Before calling the post-commit hook, the variable "pc_err" is cleared while later only "pch_error" is used. "pch_error$cmt_id" only appeared in "upvar"-Statements (which were changed to "global") and was removed. Signed-off-by: Jens Lehmann Signed-off-by: Shawn O. Pearce

git-gui: Fix post-commit status with subject in non-locale encoding

2009-02-01T22:56:54Z

As pointed out in msysgit bug #181, when a non-locale encoding is used for commits, post-commit status messages display the subject incorrectly. It happens because the file handle is not properly configured before the subject is read back. This patch fixes it by factoring out the code that is used to setup the output handle into a separate function, and calling it from the reading code. Signed-off-by: Alexander Gavrilov Acked-by: Robin Rosenberg Signed-off-by: Shawn O. Pearce

git-gui: Fix commit encoding handling.

2008-12-08T16:33:05Z

Commits without an encoding header are supposed to be encoded in utf8. While this apparently hasn't always been the case, currently it is the active convention, so it is better to follow it; otherwise people who have to use commitEncoding on their machines are unable to read utf-8 commits made by others. I also think that it is preferrable to display the warning about an unsupported value of commitEncoding more prominently, because this condition may lead to surprising behavior and, eventually, to loss of data. Signed-off-by: Alexander Gavrilov Signed-off-by: Shawn O. Pearce