git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>,
	Dakota Hawkins <dakotahawkins@gmail.com>,
	git@vger.kernel.org
Subject: Re: Issue with global config defaults "user.useConfigOnly = true" + "pull.rebase = preserve" - "user.email"
Date: Thu, 11 Aug 2016 15:44:52 -0700	[thread overview]
Message-ID: <xmqqvaz7x6vv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160729223134.GA22591@sigill.intra.peff.net> (Jeff King's message of "Fri, 29 Jul 2016 18:31:35 -0400")

Earlier, Peff sent this patch (slightly buried in a discussion) on
"rebase -i" in <20160729223134.GA22591@sigill.intra.peff.net>.

> Subject: rebase-interactive: drop early check for valid ident
>
> Since the very inception of interactive-rebase in 1b1dce4
> (Teach rebase an interactive mode, 2007-06-25), there has
> been a preemptive check, before looking at any commits, to
> see whether the user has a valid name/email combination.
>
> This is convenient, because it means that we abort the
> operation before even beginning (rather than just
> complaining that we are unable to pick a particular commit).
>
> However, it does the wrong thing when the rebase does not
> actually need to generate any new commits (e.g., a
> fast-forward with no commits to pick, or one where the base
> stays the same, and we just pick the same commits without
> rewriting anything). In this case it may complain about the
> lack of ident, even though one would not be needed to
> complete the operation.
>
> This may seem like mere nit-picking, but because interactive
> rebase underlies the "preserve-merges" rebase, somebody who
> has set "pull.rebase" to "preserve" cannot make even a
> fast-forward pull without a valid ident, as we bail before
> even realizing the fast-forward nature.
>
> This commit drops the extra ident check entirely. This means
> we rely on individual commands that generate commit objects
> to complain. So we will continue to notice and prevent cases
> that actually do create commits, but with one important
> difference: we fail while actually executing the "pick"
> operations, and leave the rebase in a conflicted, half-done
> state.
>
> In some ways this is less convenient, but in some ways it is
> more so; the user can then manually commit or even "git
> rebase --continue" after setting up their ident (or
> providing it as a one-off on the command line).
>
> Reported-by: Dakota Hawkins <dakotahawkins@gmail.com>
> Signed-off-by: Jeff King <peff@peff.net>
> ---

To which, I responded (referring to the last paragraph):

    Yup, that is the controvercial bit, and I suspect Dscho's original
    was siding for the "set up ident first, as you will need it anyway
    eventually", so I'll let others with viewpoints different from us to
    chime in first before picking it up.

Do you have a preference either way to help us decide if we want to
take this change or not?

Thanks.

>  git-rebase--interactive.sh |  3 ---
>  t/t7517-per-repo-email.sh  | 47 ++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 47 insertions(+), 3 deletions(-)
>
> diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
> index ded4595..f0f4777 100644
> --- a/git-rebase--interactive.sh
> +++ b/git-rebase--interactive.sh
> @@ -1180,9 +1180,6 @@ To continue rebase after editing, run:
>  	;;
>  esac
>  
> -git var GIT_COMMITTER_IDENT >/dev/null ||
> -	die "$(gettext "You need to set your committer info first")"
> -
>  comment_for_reflog start
>  
>  if test ! -z "$switch_to"
> diff --git a/t/t7517-per-repo-email.sh b/t/t7517-per-repo-email.sh
> index 337e6e3..2a22fa7 100755
> --- a/t/t7517-per-repo-email.sh
> +++ b/t/t7517-per-repo-email.sh
> @@ -36,4 +36,51 @@ test_expect_success 'succeeds cloning if global email is not set' '
>  	git clone . clone
>  '
>  
> +test_expect_success 'set up rebase scenarios' '
> +	# temporarily enable an actual ident for this setup
> +	test_config user.email foo@example.com &&
> +	test_commit new &&
> +	git branch side-without-commit HEAD^ &&
> +	git checkout -b side-with-commit HEAD^ &&
> +	test_commit side
> +'
> +
> +test_expect_success 'fast-forward rebase does not care about ident' '
> +	git checkout -B tmp side-without-commit &&
> +	git rebase master
> +'
> +
> +test_expect_success 'non-fast-forward rebase refuses to write commits' '
> +	test_when_finished "git rebase --abort || true" &&
> +	git checkout -B tmp side-with-commit &&
> +	test_must_fail git rebase master
> +'
> +
> +test_expect_success 'fast-forward rebase does not care about ident (interactive)' '
> +	git checkout -B tmp side-without-commit &&
> +	git rebase -i master
> +'
> +
> +test_expect_success 'non-fast-forward rebase refuses to write commits (interactive)' '
> +	test_when_finished "git rebase --abort || true" &&
> +	git checkout -B tmp side-with-commit &&
> +	test_must_fail git rebase -i master
> +'
> +
> +test_expect_success 'noop interactive rebase does not care about ident' '
> +	git checkout -B tmp side-with-commit &&
> +	git rebase -i HEAD^
> +'
> +
> +test_expect_success 'fast-forward rebase does not care about ident (preserve)' '
> +	git checkout -B tmp side-without-commit &&
> +	git rebase -p master
> +'
> +
> +test_expect_success 'non-fast-forward rebase refuses to write commits (preserve)' '
> +	test_when_finished "git rebase --abort || true" &&
> +	git checkout -B tmp side-with-commit &&
> +	test_must_fail git rebase -p master
> +'
> +
>  test_done

  parent reply	other threads:[~2016-08-11 22:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:17 Issue with global config defaults "user.useConfigOnly = true" + "pull.rebase = preserve" - "user.email" Dakota Hawkins
2016-07-29 17:47 ` Junio C Hamano
2016-07-29 18:11   ` Jeff King
2016-07-29 18:32     ` Junio C Hamano
2016-07-29 18:39       ` Jeff King
2016-07-29 18:52         ` Jeff King
2016-07-29 18:37     ` Junio C Hamano
2016-07-29 22:31       ` Jeff King
2016-07-29 22:45         ` Junio C Hamano
2016-07-29 22:49           ` Jeff King
2016-07-30 16:41             ` Dakota Hawkins
2016-08-11 22:44         ` Junio C Hamano [this message]
2016-09-09 15:32           ` Johannes Schindelin
2016-09-09 16:09             ` Junio C Hamano
2016-09-09 19:00               ` Junio C Hamano
2016-09-09 23:31                 ` Dakota Hawkins
2016-07-29 18:20   ` Junio C Hamano
2016-07-29 18:31     ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqvaz7x6vv.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dakotahawkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).