| commit | 8763dbb1b24c260243f69130c734c13563a16db6 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Sat, 16 May 2009 18:46:22 +0000 (16 11:46 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 17 May 2009 02:46:31 +0000 (16 19:46 -0700) | ||
| tree | f7b00dbc6d05080cf5b6100f255cad0d76dc80b8 | treesnapshot (tar.gz zip) |
| parent | 77ebd56dc3d2efaeac87edc990cc1b99f331527c | commitdiff |
completion: fix PS1 display during a merge on detached HEAD
If your merge stops in a conflict while on a detached HEAD, recent
completion code fails to show anything. This was because various cases
added to support the operation-in-progress markers (e.g. REBASE, MERGING)
forgot that they need to set the variable "b" to something for the result
they computed to be displayed at all.
Probably not many people make trial merges on a detached HEAD (which is
tremendously useful feature of git, by the way), and that may be why this
was not noticed for a long time.
Acked-By: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If your merge stops in a conflict while on a detached HEAD, recent
completion code fails to show anything. This was because various cases
added to support the operation-in-progress markers (e.g. REBASE, MERGING)
forgot that they need to set the variable "b" to something for the result
they computed to be displayed at all.
Probably not many people make trial merges on a detached HEAD (which is
tremendously useful feature of git, by the way), and that may be why this
was not noticed for a long time.
Acked-By: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| contrib/completion/git-completion.bash | diffblobblamehistory |