git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: John Cai <johncai86@gmail.com>,
	git@vger.kernel.org, levraiphilippeblain@gmail.com,
	phillip.wood123@gmail.com, Tilman Vogel <tilman.vogel@web.de>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3] builtin/pull.c: teach run_merge() to honor rebase.autostash config
Date: Thu, 6 Jan 2022 12:14:00 -0500	[thread overview]
Message-ID: <YdcjWG/67JlxTjfF@nand.local> (raw)
In-Reply-To: <YdcjCKTrK+W/FCw1@nand.local>

On Thu, Jan 06, 2022 at 12:12:40PM -0500, Taylor Blau wrote:
> On Thu, Jan 06, 2022 at 10:02:26AM -0500, John Cai wrote:
> > diff --git a/builtin/pull.c b/builtin/pull.c
> > index 100cbf9fb8..8423e420ee 100644
> > --- a/builtin/pull.c
> > +++ b/builtin/pull.c
> > @@ -1133,7 +1133,14 @@ int cmd_pull(int argc, const char **argv, const char *prefix)
> >  			die(_("cannot rebase with locally recorded submodule modifications"));
> >
> >  		if (can_ff) {
> > -			/* we can fast-forward this without invoking rebase */
> > +			/*
> > +			* We can fast-forward without invoking
> > +			* rebase, by calling run_merge().  But we
> > +			* have to allow rebase.autostash=true to kick
> > +			* in.
> > +			*/
> > +			if (opt_autostash < 0)
> > +				opt_autostash = config_autostash;
>
> This looks OK, and prefers the value of autostash given over options
> over the configured one. But it may be a little clearer to construct it
> that way explicitly (see the conditional "if (opt_rebase)" inside of
> cmd_pull()).

Oops, ignore this suggestion. run_merge() looks at the static variable
opt_autostash, so you really do need to be manipulating it directly.

Nevermind: what you wrote here looks fine.

Thanks,
Taylor

  reply	other threads:[~2022-01-06 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 15:02 [PATCH v3] builtin/pull.c: teach run_merge() to honor rebase.autostash config John Cai
2022-01-06 17:12 ` Taylor Blau
2022-01-06 17:14   ` Taylor Blau [this message]
2022-01-06 18:31   ` Junio C Hamano
2022-01-06 19:36     ` Taylor Blau

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=YdcjWG/67JlxTjfF@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johncai86@gmail.com \
    --cc=levraiphilippeblain@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=tilman.vogel@web.de \
    /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.
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 NNTP newsgroup(s).