Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitcmds: force option "no-abbrev-commit" when running "git log" #412

Merged
merged 1 commit into from
Feb 4, 2015
Merged

gitcmds: force option "no-abbrev-commit" when running "git log" #412

merged 1 commit into from
Feb 4, 2015

Conversation

weo
Copy link

@weo weo commented Feb 4, 2015

I have set "log.abbrevCommit = true" in my ".gitconfig" file.

In that case the "More..." items in the "Load previous Commit Message" and
"Fixup previous Commit" sub menus wont work.

The reason is the regular expression REV_LIST_REGEX. It expects the SHA1 to be
exactly 40 characters long in the git log output.

Signed-off-by: Wolfgang Ocker weo@reccoware.de

I have set "log.abbrevCommit = true" in my ".gitconfig" file.

In that case the "More..." items in the "Load previous Commit Message" and
"Fixup previous Commit" sub menus wont work.

The reason is the regular expression REV_LIST_REGEX. It expects the SHA1 to be
exactly 40 characters long in the git log output.

Signed-off-by: Wolfgang Ocker <weo@reccoware.de>
davvid added a commit that referenced this pull request Feb 4, 2015
gitcmds: force option "no-abbrev-commit" when running "git log"

Signed-off-by: David Aguilar <davvid@gmail.com>
@davvid davvid merged commit de0a696 into git-cola:master Feb 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants