public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux•intel.com>
Cc: Eric Sunshine <sunshine@sunshineco•com>, git@vger•kernel.org
Subject: Re: [PATCHv2] rebase -i: respect core.abbrev for real
Date: Wed, 21 Jan 2015 22:56:28 -0800	[thread overview]
Message-ID: <xmqqsif3uwv7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1421750552-110075-1-git-send-email-kirill.shutemov@linux.intel.com> (Kirill A. Shutemov's message of "Tue, 20 Jan 2015 12:42:32 +0200")

"Kirill A. Shutemov" <kirill.shutemov@linux•intel.com> writes:

> I have tried to fix this before: see 568950388be2, but it doesn't
> really work.
>
> I don't know how it happend, but that commit makes interactive rebase to
> respect core.abbrev only during --edit-todo, but not the initial todo
> list edit.
>
> For this time I've included a test-case to avoid this frustration again.

I suspect that the work that introduced expand/collapse could have
gone one step further so that all of the short object names you are
touching in this patch can stay in the full 40-hex name to avoid
ambiguity.  That is, keep the internal representation always use the
full object name, and then always call these three:

    collapse_todo_ids 
    git_sequence_editor
    expand_todo_ids

in this order.

Wouldn't that make the end result a lot cleaner, I wonder?


>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux•intel.com>
> ---
>  v2: fix &&-chain in the test-case
> ---
>  git-rebase--interactive.sh    | 4 ++--
>  t/t3404-rebase-interactive.sh | 7 +++++++
>  2 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index c6a4629cbc2b..1855e12f1ada 100644
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -962,7 +962,7 @@ else
>  	shortrevisions=$shorthead
>  fi
>  git rev-list $merges_option --pretty=oneline --abbrev-commit \
> -	--abbrev=7 --reverse --left-right --topo-order \
> +	--reverse --left-right --topo-order \
>  	$revisions ${restrict_revision+^$restrict_revision} | \
>  	sed -n "s/^>//p" |
>  while read -r shortsha1 rest
> @@ -1020,7 +1020,7 @@ then
>  			# just the history of its first-parent for others that will
>  			# be rebasing on top of it
>  			git rev-list --parents -1 $rev | cut -d' ' -s -f2 > "$dropped"/$rev
> -			short=$(git rev-list -1 --abbrev-commit --abbrev=7 $rev)
> +			short=$(git rev-list -1 --abbrev-commit $rev)
>  			sane_grep -v "^[a-z][a-z]* $short" <"$todo" > "${todo}2" ; mv "${todo}2" "$todo"
>  			rm "$rewritten"/$rev
>  		fi
> diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
> index 8197ed29a9ec..a31f7e0430e1 100755
> --- a/t/t3404-rebase-interactive.sh
> +++ b/t/t3404-rebase-interactive.sh
> @@ -1039,4 +1039,11 @@ test_expect_success 'short SHA-1 collide' '
>  	)
>  '
>  
> +test_expect_success 'respect core.abbrev' '
> +	git config core.abbrev 12 &&
> +	set_cat_todo_editor &&
> +	test_must_fail git rebase -i HEAD~4 >todo-list &&
> +	test 4 = $(grep -c "pick [0-9a-f]\{12,\}" todo-list)
> +'
> +
>  test_done

  reply	other threads:[~2015-01-22  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 14:20 [PATCH] rebase -i: respect core.abbrev for real Kirill A. Shutemov
2015-01-19 22:43 ` Eric Sunshine
2015-01-20 10:42   ` [PATCHv2] " Kirill A. Shutemov
2015-01-22  6:56     ` Junio C Hamano [this message]
2015-01-22 11:50   ` [PATCHv3] " Kirill A. Shutemov
2015-01-22 20:10     ` Junio C Hamano
2015-01-22 20:19     ` RFC "grep '...\{m,n\}"? Junio C Hamano
2015-01-23  0:39       ` Duy Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqsif3uwv7.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=kirill.shutemov@linux$(echo .)intel.com \
    --cc=sunshine@sunshineco$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox