git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v5] pull: allow dirty tree when rebase.autostash enabled

From
Kevin Daudt <me@ikke.info>
Date
Jul 22, 2015, 19:07 UTC
Message-ID
<20150722190724.GA11291@ikke.info>
In-Reply-To
<20150707035956.GA6105@yoshi.chippynet.com>
On Tue, Jul 07, 2015 at 11:59:56AM +0800, Paul Tan wrote:
Show 89 quoted lines
> On Mon, Jul 06, 2015 at 01:39:47PM -0700, Junio C Hamano wrote:
> > Kevin Daudt <me@ikke.info> writes:
> > 
> > > rebase learned to stash changes when it encounters a dirty work tree, but
> > > git pull --rebase does not.
> > >
> > > Only verify if the working tree is dirty when rebase.autostash is not
> > > enabled.
> > >
> > > Signed-off-by: Kevin Daudt <me@ikke.info>
> > > Helped-by: Paul Tan <pyokagan@gmail.com>
> > > ---
> > 
> > I applied it, tried to run today's integration cycle, and then ended
> > up ejecting it from my tree for now, as this seemed to break 5520
> > when merged to 'pu' X-<.
> > 
> > Well, that is partly expected, as Paul's builtin/pull.c does not
> > know about it (yet).
> 
> Yeah, sorry about that.
> 
> Here's a modified patch for the C code.
> 
> Regards,
> Paul
> 
> --- >8 ---
> From: Kevin Daudt <me@ikke.info>
> Date: Sat, 4 Jul 2015 23:42:38 +0200
> 
> rebase learned to stash changes when it encounters a dirty work tree,
> but git pull --rebase does not.
> 
> Only verify if the working tree is dirty when rebase.autostash is not
> enabled.
> 
> Signed-off-by: Kevin Daudt <me@ikke.info>
> Signed-off-by: Paul Tan <pyokagan@gmail.com>
> ---
>  builtin/pull.c  |  6 +++++-
>  t/t5520-pull.sh | 11 +++++++++++
>  2 files changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/builtin/pull.c b/builtin/pull.c
> index 722a83c..b7bc1ff 100644
> --- a/builtin/pull.c
> +++ b/builtin/pull.c
> @@ -823,10 +823,14 @@ int cmd_pull(int argc, const char **argv, const char *prefix)
>  		hashclr(orig_head);
>  
>  	if (opt_rebase) {
> +		int autostash = 0;
> +
>  		if (is_null_sha1(orig_head) && !is_cache_unborn())
>  			die(_("Updating an unborn branch with changes added to the index."));
>  
> -		die_on_unclean_work_tree(prefix);
> +		git_config_get_bool("rebase.autostash", &autostash);
> +		if (!autostash)
> +			die_on_unclean_work_tree(prefix);
>  
>  		if (get_rebase_fork_point(rebase_fork_point, repo, *refspecs))
>  			hashclr(rebase_fork_point);
> diff --git a/t/t5520-pull.sh b/t/t5520-pull.sh
> index f4a7193..a0013ee 100755
> --- a/t/t5520-pull.sh
> +++ b/t/t5520-pull.sh
> @@ -245,6 +245,17 @@ test_expect_success '--rebase fails with multiple branches' '
>  	test modified = "$(git show HEAD:file)"
>  '
>  
> +test_expect_success 'pull --rebase succeeds with dirty working directory and rebase.autostash set' '
> +	test_config rebase.autostash true &&
> +	git reset --hard before-rebase &&
> +	echo dirty >new_file &&
> +	git add new_file &&
> +	git pull --rebase . copy &&
> +	test_cmp_rev HEAD^ copy &&
> +	test "$(cat new_file)" = dirty &&
> +	test "$(cat file)" = "modified again"
> +'
> +
>  test_expect_success 'pull.rebase' '
>  	git reset --hard before-rebase &&
>  	test_config pull.rebase true &&
> -- 
> 2.5.0.rc1.21.gbd65f2d.dirty
> 
Any news about this? Is it still waiting for something?
Previous: Paul TanNext: Junio C Hamano
Message 13 of 16 in “pull: allow dirty tree when rebase.autostash enabled”
  1. pull: allow dirty tree when rebase.autostash enabledKevin Daudt, Jun 2, 2015
  2. Paul TanJun 3, 2015
  3. 1/2 t5520-pull: Simplify --rebase with dirty tree testKevin Daudt, Jun 6, 2015
  4. 2/2 pull: allow dirty tree when rebase.autostash enabledKevin Daudt, Jun 6, 2015
  5. Paul TanJun 11, 2015
  6. Kevin DaudtJun 17, 2015
  7. pull: allow dirty tree when rebase.autostash enabledKevin Daudt, Jun 17, 2015
  8. Junio C HamanoJun 17, 2015
  9. kd/Kevin Daudt, Jul 4, 2015
  10. pull: allow dirty tree when rebase.autostash enabledKevin Daudt, Jul 4, 2015
  11. Junio C HamanoJul 6, 2015
  12. pull: allow dirty tree when rebase.autostash enabledPaul Tan, Jul 7, 2015
  13. Kevin DaudtJul 22, 2015
  14. Junio C HamanoJul 22, 2015
  15. Kevin DaudtJul 22, 2015
  16. Paul TanJun 11, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.