git-commit-vandalism

Git with broken hash generation to generate collisions between object IDs. Don't use this! https://undefinedbehavior.de/posts/commit-vandalism/

Go to file

Shawn O. Pearce 6e27d826c8 git-gui: Verify we should actually perform a commit when asked to do so. A user shouldn't perform a commit if any of the following are true: * The repository state has changed since the last rescan. * There are no files updated in the index to commit. * There are unmerged stages still in the index. * The commit message has not been provided. * The pre-commit hook is executable and declined. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>	2006-11-07 03:05:16 -05:00
git-gui	git-gui: Verify we should actually perform a commit when asked to do so.	2006-11-07 03:05:16 -05:00

Shawn O. Pearce 6e27d826c8 git-gui: Verify we should actually perform a commit when asked to do so.

A user shouldn't perform a commit if any of the following are true:

 * The repository state has changed since the last rescan.
 * There are no files updated in the index to commit.
 * There are unmerged stages still in the index.
 * The commit message has not been provided.
 * The pre-commit hook is executable and declined.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>

2006-11-07 03:05:16 -05:00

git-gui

git-gui: Verify we should actually perform a commit when asked to do so.

2006-11-07 03:05:16 -05:00