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

Re: How to pre-empt git pull merge error?

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Nov 27, 2013, 15:42 UTC
Message-ID
<20131127194240.2abaff5575961b3d73e1970f@domain007.com>
In-Reply-To
<86d2llc1rs.fsf@gmail.com>

On Wed, 27 Nov 2013 15:17:27 +0000 Pete Forman <petef4+usenet@gmail.com> wrote:

Show 19 quoted lines
> I am looking for a way of detecting up front whether a git pull or git
> merge would fail. The sort of script I want to perform is to update a
> server.
> 
>     git fetch
>     git okay
>     stop server
>     backup data
>     git merge
>     start server
> 
> Here git okay is a place holder for the command I am asking for.
> 
> If a file has been changed outside of a commit then git pull fails
> with the following error.
> 
> error: Your local changes to '...' would be overwritten by merge.
> Aborting. Please, commit your changes or stash them before you can
> merge.
What's wrong with "git okay" being
if git merge whatever 2>/dev/null; then
  ... OK path
else
  ... "merge failed" path
fi
?
Previous: Pete FormanNext: Matthieu Moy
Message 2 of 7 in “How to pre-empt git pull merge error?”
  1. Pete FormanNov 27, 2013
  2. Konstantin KhomoutovNov 27, 2013
  3. Matthieu MoyNov 27, 2013
  4. Antoine PelisseNov 27, 2013
  5. Thomas RastNov 27, 2013
  6. Pete FormanNov 28, 2013
  7. Junio C HamanoNov 27, 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.