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

Re: How to update? (git Changed but not updated)

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Feb 22, 2009, 01:10 UTC
Message-ID
<slrngq19fs.vna.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<49A070B5.90909@dplanet.ch>
On 2009-02-21, Reto S. News <retoh@dplanet.ch> wrote:
Show 15 quoted lines
> Beginner question: "How to update the pushed changes on the master?"
>
> On Slave Host (a Developer that receives a working copy of a project):
>
> $ git clone git://master.example.net/test myrepo
> $ cd myrepo   # ... here I see all received files from the master
> $ Changing file "foo.txt"
> $ git add .   # ... for whatever reason this is necessary
> $ git commit -m 'I changed this file'
> $ git push
>
> On Master Host (master.example.net):
>
> # git status # Shows me correctly foo.txt has been changed by the"Slave"
> # git show   # Shows me even the made changes in a diff style!
I'll bet the changes shown are 'reversed'...
> Now I have to update the fresh content produced by the "Slave". As an
> ugly work-around, I'm currently cloning it again from localhost :-|
>
> Any suggestions are very appreciated.

Your master is a non-bare repo. Try http://git.or.cz/gitwiki/GitFaq#non-bare .

I also wrote up a much more detailed description of this at http://sitaramc.github.com/concepts-and-tips/0-terminology.html#a5 -- I hope it helps you.

Regards,
Sitaram
Previous: Reto S. NewsNext: Rainer Blome
Message 2 of 4 in “How to update? (git Changed but not updated)”
  1. Reto S. NewsFeb 21, 2009
  2. Sitaram ChamartyFeb 22, 2009
  3. Rainer BlomeFeb 22, 2009
  4. Reto SchärFeb 22, 2009

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.