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

Re: [PATCH 3/3] git-pull.sh: introduce --[no-]autostash and pull.autostash

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 24, 2013, 07:28 UTC
Message-ID
<7va9pt2r4e.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALkWK0=oOt0teGqCjpDkerR3-t1cY=qKyK-AtoLLCz9L1-+vyw@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 10 quoted lines
>>> +     elif test "$autostash" = false
>>> +     then
>>>               require_clean_work_tree "pull with rebase" "Please commit or stash them."
>>>       fi
>>
>> A safety net, after you run "git stash", to validate that the
>> added "git stash" indeed made the working tree clean, is necessary
>> below, but there does not seem to be any.
>
> Um, isn't that part of the "git stash" testsuite?

You should always "trust but verify" what other commands do at key points of the operation; and I think this "require-clean-work-tree" is a key precondition for this mode of operation to work correctly.

Especially because you do not even bother to check the result of "git stash" before continuing ;-).

Show 18 quoted lines
>>> +if test "$autostash" = true && stash_required
>>> +then
>>> +     git stash
>>> +     eval "$eval"
>>> +     test $? = 0 && git stash pop
>>> +else
>>> +     eval "exec $eval"
>>> +fi
>>
>> Delaying to run "git stash" as much as possible is fine, but with
>> the above, can the user tell if something was stashed and she has
>> to "stash pop" once she is done helping the command to resolve the
>> conflicts, or she shouldn't run "stash pop" after she is done
>> (because if nothing is stashed at this point, that "pop" will pop an
>> unrelated stash)?
>
> I could easily tell, from the "git pull" output: if conflict, then
> stash hasn't been applied.

The question was about "git stash save". Depending on the cleanness of the tree when "git pull" was started, "save" may or may not have been done. After resolving a conflicted "git pull" and committing the result, the user does not have much clue if she needs to pop anything, does she? Instead of the usual "resolve the conflicts and commit the result", she may need to see "resolve the conflicts, commit the result, *AND* UNSTASH".

Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 9 of 11 in “Introduce pull.autostash”
  1. 0/3 Introduce pull.autostashRamkumar Ramachandra, Mar 22, 2013
  2. 1/3 git-pull.sh: prefer invoking "git <command>" over "git-<command>"Ramkumar Ramachandra, Mar 22, 2013
  3. 2/3 t5521 (pull-options): use test_commit() where appropriateRamkumar Ramachandra, Mar 22, 2013
  4. Junio C HamanoMar 22, 2013
  5. Ramkumar RamachandraMar 23, 2013
  6. 3/3 git-pull.sh: introduce --[no-]autostash and pull.autostashRamkumar Ramachandra, Mar 22, 2013
  7. Junio C HamanoMar 22, 2013
  8. Ramkumar RamachandraMar 23, 2013
  9. Junio C HamanoMar 24, 2013
  10. Ramkumar RamachandraMar 24, 2013
  11. Ramkumar RamachandraMar 24, 2013

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.