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

Re: Commit changes to remote repository

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jan 14, 2012, 14:27 UTC
Message-ID
<vpqboq6fjfy.fsf@bauges.imag.fr>
In-Reply-To
<20120114113141.GG2850@centaur.lab.cmartin.tk>
Carlos Martín Nieto <cmn@elego.de> writes:
Show 6 quoted lines
> You're trying to push to a non-bare repository and change the
> currently active branch, which can cause problems, so git isn't
> letting you. There's an explanation of bare and non-bare at
> http://bare-vs-nonbare.gitrecipes.de/ but the short and sweet is that
> you should init the repo you want to use as the central point with
> --bare and do modifications locally and then push there.
An alternative is to push to a temporary, non-checked-out branch.
I sometimes do
  laptop$ git push desktop HEAD:incomming
and then
  desktop$ git merge incomming

The push does not disturb the worktree on the desktop, and the merge is done manually on the receiving machine.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Carlos Martín NietoNext: Junio C Hamano
Message 3 of 4 in “Commit changes to remote repository”
  1. rupertyJan 13, 2012
  2. Carlos Martín NietoJan 14, 2012
  3. Matthieu MoyJan 14, 2012
  4. Junio C HamanoJan 17, 2012

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.