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

Re: After successful push, all files are listed as modified, uncommitted changes on origin server

From
Jakub Narebski <jnareb@gmail.com>
Date
Apr 28, 2008, 15:40 UTC
Message-ID
<m33ap6oump.fsf@localhost.localdomain>
In-Reply-To
<1d2b97db0804280834g8457151q658f54ff66e469@mail.gmail.com>
"Tyler Silcox" <tsilcox@gmail.com> writes:
Show 13 quoted lines
> Myself and another developer are both experiencing this 'issue'. We
> will run a local commit and pull (on Macs), then push to the origin
> server (which is on Windows.) If you view the git status, it will list
> all files as modified, but I can't pull any details about what was
> modified with diff. In gitk, it shows all the files under 'local
> uncommitted changes, not checked in to index', but again, it doesn't
> tell me what was changed, it just lists the file names in the left
> column.
> 
> I'm thinking it's an OSX file browser process that is modifying the
> files' meta data when git is checking the repository. It is not
> affecting our workflow, but it is an annoyance. Any info that can help
> prevent this would be appreciated.

This is not the case of "do not push into non-bare repository"? Or different autocrlf on both machines?

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Tyler Silcox
Message 2 of 2 in “After successful push, all files are listed as modified, uncommitted changes on origin server”
  1. Tyler SilcoxApr 28, 2008
  2. Jakub NarebskiApr 28, 2008

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.