diff options
author | Kirill A. Shutemov <kirill.shutemov@linux.intel.com> | 2015-01-22 13:50:15 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2015-01-22 12:19:47 -0800 |
commit | edb72d551128f798f5f43292789cb7c731d1e01f (patch) | |
tree | c0f7a8a824e4bfbeefd230b3edc2d8f033a41451 /t/t7605-merge-resolve.sh | |
parent | Merge branch 'maint-2.0' into maint-2.1 (diff) | |
download | tgif-edb72d551128f798f5f43292789cb7c731d1e01f.tar.xz |
rebase -i: use full object name internally throughout the script
In earlier days, the abbreviated commit object name shown to the end
users were generated with hardcoded --abbrev=7; 56895038 (rebase
-i: respect core.abbrev, 2013-09-28) tried to make it honor the user
specified core.abbrev, but it missed the very initial invocation of
the editor.
These days, we try to use the full 40-hex object names internally to
avoid ambiguity that can arise after rebase starts running. Newly
created objects during the rebase may share the same prefix with
existing commits listed in the insn sheet. These object names are
shortened just before invoking the sequence editor to present the
insn sheet to the end user, and then expanded back to full object
names when the editor returns.
But the code still used the shortened names when preparing the insn
sheet for the very first time, resulting "7 hexdigits or more"
output to the user. Change the code to use full 40-hex commit
object names from the very beginning to make things more uniform.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7605-merge-resolve.sh')
0 files changed, 0 insertions, 0 deletions