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

Re: Problem with git push over <hostname>:/path protocol (ssh)

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 24, 2007, 20:35 UTC
Message-ID
<ep8fss$dlf$1@sea.gmane.org>
In-Reply-To
<Pine.LNX.4.64.0701241453410.20138@iabervon.org>
Daniel Barkalow wrote:
Show 9 quoted lines
>> So, if the developer then commits on his branch on machine 1, all his
>> changes get undone.  This has happened to him consistently --- he is
>> running git 1.4.4.1 throughout.  I just reproduced it using the above,
>> and I am using 1.5.0-rc2 on machine 2, and 1.4.4.1 on machine 1.
> 
> Git gets unhappy if you push into a branch that's checked out. It doesn't 
> update the index or working directory, so the state after the push looks 
> like the user reverted the patch in the working directory and updated the 
> index.
So you usually push into _bare_ repository, or use fetch / pull instead.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Bill LearNext: Bill Lear
Message 6 of 7 in “Problem with git push over <hostname>:/path protocol (ssh)”
  1. Bill LearJan 24, 2007
  2. Daniel BarkalowJan 24, 2007
  3. Bill LearJan 24, 2007
  4. Jakub NarebskiJan 24, 2007
  5. Bill LearJan 24, 2007
  6. Jakub NarebskiJan 24, 2007
  7. Bill LearJan 24, 2007

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.