Re: [PATCH] Show number of commits being rebased interactively

[Junio C Hamano <gitster@pobox.com>]

Onno Kortmann <onno@gmx.net> writes:

> Hi,
>
>> These lines above "---" will become the only log message text, which
>> is probably not what you intended.  Use "-- >8 --" marker instead
>> (that is a perforation line with a pair of scissors on it)?
> Thanks, hopefully fixed below.
>
>>> +commitcount=$(git stripspace --strip-comments <"$todo"  | wc -l)
>>
>> Does this count the number of commits?  I suspect it at least needs
>> to filter "x|exec" out.
> Very true - after reading this, I learned about the '-x' option
> to git-rebase -i :-)
> I changed the patch so it now properly looks for '^pick ' patterns. I

Hmm, is looking only for pick the right thing?

Stepping back a bit, I have to wonder what we want to count.  The
number of commits after the rebase is done, or the number of commits
in the input of the rebase operation?

The generation loop that reads from rev-list may add only "pick",
but then rearrange_squash will munge some into squash and fixup.  We
may even have some more automated editing of the insn sheet in the
future, just like add_exec_commands were added, so I think it is
more prudent to go from the full list of possible insn sheet
commands (that is, pick, reword, edit, squash, fixup and exec) and
count them, not just relying on "we know the rev-list loop happens
to add only pick commands".

> In the case of having 'exec' lines interspersed, the $commitcount
> becomes a lot less useful (no comparison to editor line numbers),
> though.

Hmph, interesting.  Then perhaps not filtering at all and instead
labelling this new piece of information not "commit(s)" a better
solution?  You are counting the number of instructions in the insn
sheet, so perhaps something like "($count todo items(s))" or
something?

> Onno
> 8< 8< 8< 8< 8< 8< 8< 8< 8<

That is not a scissors line, I suspect.

I didn't try running "git am" on this message, though.  Did you?

> Subject: [PATCH] Show number of commits being rebased interactively
>
> During 'rebase -i', one wrong edit in a long rebase session might
> inadvertently drop commits. This change shows the total number of
> commits in the comments below the commit list. After the rebase
> edit, the number can be quickly compared to the line number of
> the last commit - by scrolling to the last entry in the rebase
> TODO list. This gives peace of mind that no commits have been
> lost in the edit.
>
> Signed-off-by: Onno Kortmann <onno@gmx.net>
> ---
>  git-rebase--interactive.sh | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index b64dd28..b26e5e6 100644
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -1031,9 +1031,13 @@ test -s "$todo" || echo noop >> "$todo"
>  test -n "$autosquash" && rearrange_squash "$todo"
>  test -n "$cmd" && add_exec_commands "$todo"
>
> +commitcount=$(git stripspace --strip-comments <"$todo"  | \
> +	      sane_grep "^pick " | \
> +	      wc -l)

Just a scripting tip.  When a line ends with a vertical bar (pipe),
the shell parser knows that you haven't finished speaking, so there
is no need to have "\" there.

>  cat >>"$todo" <<EOF
>
> -$comment_char Rebase $shortrevisions onto $shortonto
> +$comment_char Rebase $shortrevisions onto $shortonto ($commitcount commit(s))
>  EOF
>  append_todo_help
>  git stripspace --comment-lines >>"$todo" <<\EOF